BuildWithHQ is three things at once: a visual application builder, a dedicated runtime for every application you create, and an accountability layer that records what the application actually did. Each part is useful alone. Together they cover the gap that makes teams abandon low-code halfway through.
Every capability on this site sits in one of these three layers. If a feature doesn't make building faster, keep a boundary honest, or produce evidence, it doesn't belong in the product.
Pages, data models, workflows, permissions, and menus are configured rather than coded. Most of an application is a few days of work instead of a few months.
Three databases and an isolated code container provisioned per application. When you need real code, your developer writes real code.
Reads, exports, AI retrievals, and the authorization decisions behind them are written to an append-only database the application cannot rewrite.
Tenant provisioning, custom domains, per-customer billing, entitlements, and payouts, so reselling is built in rather than assembled.
Drag-and-drop pages, raw JSON editing, custom modules and fields, and per-tenant page forks that let your customers make their own small changes.
Three dedicated databases and an isolated container per application, and what that actually changes in a security review.
One permission model across every read path, plus field-level read logging and replayable authorization proofs.
Permission-resolved retrieval, insights that inherit access from their source record, harness packs, and per-user agents with approval queues.
Outbound calls, inbound endpoints, webhooks, server-side credentials, queues, retries, and idempotency.
Background automation with approvals, waits, branching, retries, and version isolation when you edit a live process.
Email, SMS, web leads, and internal messages in one conversation model, each thread a first-class record.
Pin any record and turn its permitted recursive graph into a living workplace for people, GoClaws and workflows, with Record Pulse, stale-work detection and Graph Playback.
Per-field encryption that removes itself from search and AI retrieval, enforced by the database rather than by convention.
A structured interview produces a blueprint you review before anything is created, then materializes it into a real application.
Assistants that act inside one person's permissions, propose consequential actions for approval, and run under a server-side quota.
Four permission-aware MCP layers for the builder account, isolated developer VM, individual SaaS application, and the SaaS builder's own end customers.
Full export with manifest and checksums, for you and for the companies using your application.
AI insights, what's new, favorites, and permission-aware search, plus white-label user documentation.
Charge your own customers, with Stripe Connect handling collection and payouts, and a partner channel for MSPs.
The list below is what exists the moment an application is provisioned, before you have configured anything specific to your business.
Sign-in, TOTP enrolment, recovery codes, session listing, and administrative session revocation.
Email, SMS, web leads, and internal messages in one thread model, each conversation a first-class record.
Pin a record, work its recursively related context with humans and GoClaws, detect stalled work, and rewind the workplace with Graph Playback.
Events bound to the same record layer, so a meeting inherits the same permissions as the deal it belongs to.
Background automation with approvals, waits, branching, retries, and version isolation on live edits.
Subscription and invoice handling through Stripe, including dunning and grace periods.
Run history, access logs, and an audit trail that records denied attempts alongside successful ones.
Uploads attached to records, included in exports rather than stranded outside them.
Chat, insights, and suggested actions scoped to what the signed-in user is permitted to see.
No. The visual layer covers pages, data models, workflows, and permissions. Anything it cannot express is written as normal code and runs in an isolated container that the platform calls through a declared API contract.
The standard deployment is hosted. A partner program exists for managed service providers who want to deploy on their own hardware and resell to their client base.
Starting from a blueprint template, a working application with your data model, pages, and permissions is typically a matter of days. The build guides in the documentation walk through complete examples end to end.
Create an account, explore the full builder console, and launch your first application on a custom domain. Nothing is charged while your application is still in development.
No credit card required. The console preview, the documentation, and the architecture reference are all readable before you sign up.
Get started free Read the docsCompose React pages in the Puck page designer, configure themes, assets, menus and User Types, and publish a reviewed page version. User Types select the experience; DataRoles and Locations control access to business records. A saved draft is separate from the version customers see.
Read the guideFor records that support Personal, explicitly choose Personal or an eligible DataRole. Personal records belong to their owner and have no location. Chat Rooms, Discussion Boards, Knowledge, Company News and Files are shared-only: choose one DataRole. For shared records, choose an authorized location or All when permitted; a blank location is not All. Child records inherit their parent’s scope. A shared record cannot be converted to Personal.
Read the guideAI search and Knowledge Core use the current user’s record, field, DataRole, location and AI-read permissions before assembling context. Multimodal retrieval can retain document text and visual evidence. Model serving, ingestion and execution workers must be configured and enabled; seeing an AI control does not establish that a provider or worker is running.
Read the guideAn app has routed Core, Logs and AI database planes. Provisioning is a staged operation: wait for readiness and any reported setup requirements before inviting customers. Marketplace presentation installs are pinned snapshots; upgrading a template is explicit. Customer-hosted Appliance operation and optional extension compute have their own deployment requirements.
Read the guideChat rooms and messages require current room membership as well as DataRole and location access, including when opened through Graph, Activity or Favorites. Find them in native Chat Rooms search; general and AI search exclude chat content. Administrators add eligible members, and saves check current authority again. Room removal preserves history through soft deletion; an authorized restore does not revive independently removed messages.
Read the guide