One brief.
Five honest stages.
Brikar does not hand you a black box. Each run has a durable job record, stage timeline, verified progress, retry history and an artifact with a manifest. Here is exactly what the system does.
Brief locked
The latest specification revision is snapshotted for the run. Editing is paused while a run is active so the artifact matches a known brief.
spec revisionGeneration
The provider produces a file bundle for the chosen framework. In live mode this is an OpenAI-compatible model; local mode uses maintained starter templates.
provider callStatic validation
Required entry points must exist, JSON manifests must parse, paths are normalized and the bundle size is bounded. This is not called a framework build.
entry points + pathsPackaging
Files are written to private artifact storage, zipped, checksummed and recorded with a manifest. Neon stores ownership and metadata, not the source archive.
sha256 + manifestHandoff
The job becomes ready only after the artifact exists. You can download the ZIP and, for web projects, open the sandboxed static preview.
artifact readyOnly supported stacks appear.
The server owns the platform and framework catalogue. A framework is offered only when its template, entry-point checks and download path are maintained.
Web app
Framework choice is immutable after project creation. To switch, create a new project.
Mobile app
Framework choice is immutable after project creation. To switch, create a new project.
Priority is real. So is backpressure.
Pro jobs sort ahead of Free jobs with bounded fairness. Provider rate limits requeue the job with exponential backoff instead of failing it. The estimate accounts for the current queue.
Priority weight 100 vs 10. Free jobs still progress.
Up to 4 attempts with backoff and a visible retry stage.
Measured from real iteration and build time. Recalculated as the run progresses.
Stage timeline and verified percentage, not model claims.
Owner checks
Every route verifies the session and project owner.
Sandboxed preview
CSP sandbox, no network egress, same-origin frame only.
Neon metadata
Source lives in private artifact storage, not the database.
Artifact integrity
ZIP checksum, file manifest and build status are stored.
Ready to put a brief through the pipeline?
Create a projectYour next codebase
starts with a sentence.
Sign in with Google, choose a platform, and write the brief. Brikar handles the queue, retries, progress and packaging.