Published surface
Runtime source
Open the live UI from a released candidate
Product | Agentic App Builder | Runtime
Run the published surface with durable state, queues, and review edges intact.
The live product opens from a released surface, not a mutable draft. Operators, queues, and approvals stay attached to the same runtime-backed UI contract.
This view is for teams that want to inspect the production posture after publication.
Durable queue state
Operator posture
Keep actions, approvals, and audit tied to runtime
Shared contract
One system
The app, the flow, and the operator all use the same primitives
Runtime-backed views
Build forms, tables, and operator panes that open onto real stored state.
Preview before release
Compare drafts and runtime candidates without mutating the live surface.
Published releases
Runtime opens from a released surface instead of a live builder draft.
Shared review edges
Actions, inbox rows, and approvals stay in the same product shell.
Features
Builder controls on the left, runtime shape on the right.
Keep the design surface and runtime output legible in one scan.
View builder
Arrange fields, panels, and operator actions in one rigid surface.
Prompt slots
Keep system instructions and runtime placeholders adjacent to the UI that uses them.
Preview states
Flip between draft, review, and runtime postures before publishing.
Runtime bindings
Map widgets onto stored records, queues, and read models without hand wiring every edge.
Release history
Compare published candidates and reopen earlier states safely.
CLI hooks
Script the same publish and preview steps outside the browser when needed.
import { createApp } from "@placeholder/builder"
const surface = createApp("agentic-app-builder")
surface.view("operator-home")
.field("company_name")
.panel("review_queue")
.action("publish_candidate")
await surface.preview("draft-02")
await surface.publish("candidate-a")
from placeholder.builder import AppBuilder
surface = AppBuilder("agentic-app-builder")
surface.view("operator-home")
surface.panel("review_queue")
surface.action("publish_candidate")
surface.preview("draft-02")
surface.publish("candidate-a")
let mut surface = AppBuilder::new("agentic-app-builder");
surface.view("operator-home");
surface.panel("review_queue");
surface.action("publish_candidate");
surface.preview("draft-02")?;
surface.publish("candidate-a")?;
Terminal Output
$ psi-builder publish candidate-a
Connecting to runtime...
✓ Builder state loaded
✓ Preview candidate frozen
✓ Runtime schema validated
✓ Release candidate published in 34ms
Published surface: operator-home
Open core surface
One product shell, three clear ways to run it.
Flat, square, and easy to scan. Keep the deployment posture visible without turning the page into an infra memo.
Local design
Sketch the app surface, preview layout changes, and test state transitions against placeholder records.
Managed runtime
Publish the surface into a hosted runtime where queues, policies, and operator context are already wired in.
Private deploy
Keep the same builder-to-runtime posture while moving the final boundary into your own environment.
Performance
Fast UI state over runtime-backed app surfaces
Read release posture, state access, and runtime responsiveness without turning the product page into a systems lecture.
Latency
Query latency
@placeholder builder load on shared runtime
WarmCold
Contact us to review deployment posture, release workflow, and runtime sizing for the builder shell.
Technical specs
Publish throughput (per surface)18 publishes/min
Concurrent previews24 active candidates
Stored UI schemas250k
Runtime bindings per surface1k+
Release retentionconfigurable
Zero-ops infra
┌───────────────────────────────┐
│ Builder Layer │
│ Draft views / preview states │
│ Publish candidates │
└───────────────────────────────┘
↕ Shared runtime
┌───────────────────────────────┐
│ Runtime Layer │
│ Queues / read models / policy │
│ Inbox / audit / actions │
└───────────────────────────────┘
A builder surface only feels trustworthy when the release posture is obvious and the runtime bindings stay durable after publication.
- Separate draft and runtime state
- No manual environment drift
- Hosted or private deployment posture
- Large UI state belongs in durable storage
- Preview candidates should not mutate live runtime
- Review edges stay attached to the released surface
Enterprise
Run the same shell with a clearer boundary when deployment posture matters.
Keep the enterprise block square and quiet. The ASCII does the explanatory work.
Tenant boundary
Keep application data inside the environment that already owns it.
Runtime separation
Builder control and release services can stay isolated from app data and operator traffic.
Managed posture
Backups, release history, and audit mirrors stay consistent with the hosted shell.
Boundary layout
▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓ ▓░ ┌────────── YOUR VPC ──────────┐ ░▓ ▓░ │ █ APP DATA █ │ ░▓ ▓░ │ stored records / attachments│ ░▓ ▓░ └──────────────────────────────┘ ░▓ ▓░ ▼ ░▓ ▓░ ┌────────── PSI* VPC ───────────┐ ░▓ ▓░ │ █ BUILDER CONTROL █ │ ░▓ ▓░ │ publish / preview / backups │ ░▓ ▓░ └──────────────────────────────┘ ░▓ ▓░ ✓ tenant boundary ✓ backups ░▓ ▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓