Overview Getting started

Welcome to BuildWithHQ

From builder account to active app, blank shell, first publish, and runtime delivery.

Create SaaS product

Set up your organization

Six steps — two down. Each step unlocks the next.

Create your account Done

Organization and owner created; your 10-day trial started — no card needed.

Verify your email Done

Verified — SaaS creation and team invitations are unlocked.

Create your first SaaS product Up next

Start blank immediately, or choose an exact published immutable template version when one is available.

Invite your team —

Add members with scoped roles: Admin, Developer, Billing, Viewer.

Add a payment method —

Convert any time before the trial ends; Stripe checkout, confirmed by webhook.

Connect a custom domain —

Cloudflare-verified hostnames with automatic TLS put your brand on your product.

Your trial

Trial ends: Aug 7, 2026
Plan: Starter (trial)
Payment: Not on file

Add payment method

Need help?

Common things to do

Create a SaaS product

Describe it to Build-with-AI or start from a template pack — either way you get a provisioned, customizable app.

Start building

Browse the template library

Versioned, pinned packs with drag-and-drop page editing and selective upgrades.

Open library

Invite your team

Role-scoped access with owner override; invitations arrive as one-time email links.

Invite members

Connect a domain

Cloudflare-verified custom hostnames with automatic TLS and a primary-domain badge.

Add domain

Set up backups

Scheduled backups per product, with your own destinations supported.

Configure

Explore the marketplace

Install vetted extensions and appliance packages into your products.

Browse

Frequently asked questions

How the platform behaves, in plain terms.

How long is the trial, and do I need a card?

The trial runs 10 days with no card required. Add a payment method any time to convert. If the trial lapses, the account locks changes but stays readable for 30 days — converting restores everything.

Why can't I create a SaaS product or invite anyone yet?

Email verification is required first. The moment you verify, SaaS creation and team invitations unlock; the banner disappears on its own.

What actually gets created with my SaaS product?

plus routing, storage allocations, usage meters, tenant-root security, and an optional container runtime. BuilderOnly apps can remain at container status NotStarted.

Blank app vs template pack — which should I use?

A blank app is always available and creates a valid shell with an empty Home page. A template pack is selectable only after an exact immutable version has a valid manifest, fingerprints, members, and at least one page. Both paths end in the same isolated app database and runtime contract.

How do custom domains work?

Add the hostname on the Domains page; verification runs through Cloudflare Custom Hostnames and TLS is issued automatically. The primary-domain badge shows live status.

How do storage limits work?

Your plan plus add-ons set pooled allocations for database, file, and AI storage. Warnings appear at 80% of a pool; add-ons extend headroom without migration.

Can one email belong to multiple organizations?

Yes. At sign-in, once your password verifies you pick which organization to enter.

What happens when I add a payment method?

You complete Stripe checkout; the conversion is confirmed by webhook, trial flags clear, and Billing shows the live subscription. If a later payment fails, service continues through a grace period while you fix it.

Where do my tenants' payments fit in?

Your SaaS bills its own end customers inside its own database. Platform revenue share runs through Stripe Connect on the tenant plane — separate from this portal, which only bills your builder subscription.

About this page

Tracks the real server-derived path: builder account, verified access, app registration, physical database trio, tenant root and bridges, blank shell or immutable template version, first page publication, runtime contract, and optional domain or container work.

Behind this page/getting-started · authenticated

Retrieve

sp_Builder_GetAccountAdminDashboard supplies the trial state, verification flag, and app/team/payment counts that drive each checklist step; the lock banner reads sp_Builder_GetAccountAccessState. sp_Builder_GetOnboardingState returns the computed checklist in one read — email verified, MFA, payment method, app/team/domain counts; dismissal persistence stays out until it is a product requirement.

Save

Read-only page. Every CTA routes to its own page with its own contracts; nothing is written here. FAQ copy is static frontend content.

Success

Checklist state comes from server truth, never localStorage.
Blank-app creation remains available when no published template version exists.
App activation does not wait for optional custom-domain verification.
BuilderOnly apps may be Active while container status remains NotStarted.

CLI handoff

Implement this scaffold from the structured contract, then remove hard-coded preview rows. The source of truth is CLI Handoff and admin-cli-manifest.json.

Page IDgetting-started

Route/getting-started

Accessauthenticated

Statusjourney-aligned-scaffold

Server-inject identity and scope values; never trust browser-supplied account, app, tenant, user, entitlement, price, or permission identifiers. Preserve the loading, empty, forbidden, failed, retrying, and completed states shown by the preview.