JRI.AI Apps System

Build the operating tool your team keeps asking for.

Start with a clear brief—“show me pipeline health”, “surface low stock”, “give our team a cleaner intake”—then build, inspect, version and publish the app inside Amplify with controlled workplace context.

Open Apps Explore Amplify

←App: Pipeline health155 left · AI credits

PreviewProblemsCodeConsolePublish

pipeline-health.apps.jri.ai· not published yet↗

↗Pipeline health

OverviewAccountsActivity

Revenue workspace

Keep the next action visible.

4 need attention

18Active deals

₹48.2LWeighted pipeline

03Due today

Atlas FoodsProposalFollow up todayAt risk

Meadow CareDiscoveryStakeholder missingWaiting

Crescent LabsNegotiationCommercial reviewOn track

The complete build loop

From a sentence to a hosted app, with decisions visible.

The builder does more than generate a page. It keeps generation conversational, shows file operations as they happen, separates preview from persistence, and keeps every accepted version recoverable.

Brief

Start with the operation that is missing—such as a pipeline-health view for deals that need attention. Add workplace house rules and choose JRI Ultra, JRI Lite, or an approved bring-your-own model connection.

Build

The builder plans, writes complete files, makes targeted edits, and streams a live file-by-file task list so progress is visible.

Inspect

Use Preview, Code, Console, and Problems. Select an element, inspect a diff, change device width, or send a runtime problem back to Fix with AI.

Apply

A build remains unsaved until it is accepted. Apply persists the version; Discard leaves the current app unchanged and does not spend another build.

Version

Open file diffs, review build history, restore an earlier version, connect a repository, and keep a visible synchronization trail.

Publish

Publish a selected version to a JRI-hosted app URL. Domain, data, and backend settings remain explicit in the workbench.

The workbench

Build, inspect, and recover in one place.

The app stays mounted while you move between views. Device controls, element selection, file diffs, console output, compile errors, media, history, settings, and publishing remain part of the same workbench.

Inventory command

What needs attention today?

12 low stock

4 purchase drafts

2 locations

Start well

Use a template or describe the exact operation.

The Apps dashboard holds app cards, templates, creation, archive controls, and a plan-aware usage meter. Each app opens into its own workbench and version history.

Pipeline health app

Give a sales or relationship team a focused view of stages, deal value, owner actions and risk.

Operations dashboard

Turn live workplace records into a focused internal command view.

Inventory tool

Inspect products, stock, purchases, and attention states across locations.

Request workflow

Create a guided intake, review, or team process around a repeatable operation.

Internal apps

Use workplace data without turning a published app into a back door.

Internal apps can read bounded JRI data through a purpose-built interface. The runtime deliberately changes based on where the app is opened.

Live team use and preview

Short-lived. Workplace-scoped. Read-only.

A dedicated token resolves the workplace server-side and exposes only supported record types. It is minted for the member open and is not the member’s JRI session.

External and published use

Bounded snapshot. No live private access.

Publishing captures a point-in-time snapshot of only the known data types referenced by the app. Public visitors do not reach the workplace’s live private records.

Overview

Compliance

Roadmap

Brand

Social

Inventory

Team

Sensitive fields such as bank account numbers, private document URLs, and social tokens are not part of the app data catalog.

Workbench settings

The generated UI is only one part of the product.

Settings govern how the app is built, what data it can use, where its source goes, and how the published version is reached.

Data and sharing

Choose whether an app reads JRI workplace data, uses a publish-time snapshot, or connects to an external backend.

House rules and AI

Set persistent design and product rules for the workplace, select a JRI model tier, or use an approved private key.

Domains

Manage the JRI app URL and the custom-domain verification path from the workbench settings.

GitHub

Connect a repository in the owner’s GitHub account, push, pull, disconnect, and inspect synchronization history.

Publish path

A real URL, TLS, versions, and a serving model designed for generated apps.

JRI assembles the accepted files into a client-routed application, compiles supported JSX and TypeScript, resolves approved packages, and serves the published version through the JRI app domain.

your-app.apps.jri.ai

Assemble

Styles, modules, imports, and client routes become one serveable application.

Publish

The selected version and its permitted data snapshot become the live release.

Serve

The hostname resolves only to a published app, with on-demand TLS guarded against unknown slugs.

Product scope

What is available now, and what is deliberately staged.

Capability	State	Practical meaning
JRI-hosted app URL	Available	Published apps use {slug}.apps.jri.ai with on-demand TLS.
Client-routed multi-page experience	Available	Apps are single-page builds with client routing, JSX/TSX compilation, and approved package resolution.
Internal workplace data	Available	Team preview uses a scoped read-only token; public publishing uses a bounded point-in-time snapshot.
External Supabase	Manual connection	URL and anon key only. One-click OAuth is a later product stage.
Custom-domain publishing	Staged rollout	Verification UI exists; production ingress is enabled only when the domain path is confirmed.
Serverful applications	Later	The current product is static-first with controlled APIs. Dedicated serverful runtimes are deferred.

Agent-driven building still has approval levels.

App, deployment, domain, GitHub, and Supabase tool groups sit behind policy states: automatic, user confirmation, owner confirmation, or blocked. Confirmed actions and tool use remain auditable.

Auto

User confirm

Owner confirm

Blocked

Build the small system your team keeps asking for.

Apps availability, build credits, quotas, model access, data connections, and publishing options depend on the workplace plan and configuration.

Open Apps Talk to JRI.AI