Y YapBuild
YapBuild / Publishing workspace

Build it. Share it. Stay in control.

One simple place to review a supported app, publish it privately, share an approved form, and manage updates. You choose when an app or form becomes public.

Supported formsPublic sharing is available for owner-reviewed forms. Visitors sign in to submit responses.
Custom full-stack appsPrivate source review and signed private builds only. Paid public-code hosting is not activated.
Your build-to-share journey

Six steps, one workspace

Follow these steps for supported YapBuild apps and reviewed forms. Full-stack customer-code hosting is separately gated until production release and billing verification.

Sign in to see your progress
Your next action

Start with your idea

Describe what you need in YapBuild chat. Publishing stays private until you choose otherwise.

Create an app in chat
Verified account progress0 of 20 of 2Counts only private publication and approved public sharing. Drafts and version history remain available without being counted as completed actions.
  1. 01Describe your appStart with a prompt in YapBuild chat.Build in chatAvailable
  2. 02Review and previewCheck the result and any backend source before approving a build.Review sourceAvailable
  3. 03Publish privatelyMake a supported app available to your account.Manage appsNot yet verified
  4. 04Share with othersShare only an explicitly reviewed form. Private records stay private.Sharing controlsNot yet verified
  5. 05Update or restoreManage revisions and restore a prior configuration.Version historyNot yet verified
  6. 06Manage or deleteStop sharing, open your private app, or permanently delete its data.Application controlsNot yet verified

Progress comes from your current account's verified app and sharing records. It does not certify a generated backend release or prove previous deleted apps existed.

Customer-code publishing

Full-stack Go projects require a verified private build, active hosting entitlement, scoped billing reservation, and signed public release approval.

Public release gated
1. SourceSave exact files and inspect SHA-256
2. Private buildApprove a single scanned, isolated build
3. BillingConfirm a genuine paid hosting entitlement and cost allowance
4. Public releaseSign publish, verify HTTPS and tenant isolation, then enable rollback and deletion

The demo is a local simulation only. Public release, rollback and deletion of generated code are not offered on this page. No payment or cloud deployment is triggered by viewing this workflow.

Separate from supported forms

YapBuild hosting plans

Not accepting new payments

Owner-approved monthly USD hosting prices, separate from your YapThing subscription. These prices are established, but enrollment and deployment are not yet open. Request early access without paying. Applicable taxes will be shown during Stripe checkout when it becomes available.

Starter$12.99 /mo1 isolated app · 2 approved builds per month · $2 planned cloud-runtime budget allowance
Growth$39.99 /mo3 isolated apps · 10 approved builds per month · $8 planned cloud-runtime budget allowance
Studio$99.99 /mo8 isolated apps · 30 approved builds per month · $25 planned cloud-runtime budget allowance

No payment information required. Requesting access does not reserve a server or begin a subscription.

Full-stack hosting checkout is paused. No charge can be started from this page.

List prices are confirmed for future activation; included capacity and runtime allowances remain prelaunch terms until service certification. No charge is possible here today. No automatic overages. Once launched, applicable tax is added and the full recurring total is reviewed in Stripe before payment. Storage, egress, AI/API calls, domains and external databases may need separately agreed allowances. No public full-stack deployment is enabled by a price selection.