DOCUMENTATION

Shipsite documentation

Shipsite turns a keyword, product idea, or existing repository into an evidence-backed site you can review, preview, release, and keep operating.

CURRENT PRODUCT CAPABILITIES2026-07-31

Start

Create your first sitePlanning works without connecting third-party accounts. Add credentials only when a later step needs them.

Plan and build

Workflow, artifacts, and gatesThe pipeline combines model-driven specialist work, deterministic checks, durable artifacts, and three Owner decision domains.Studio workspaceStudio is organized around Plan, Build, and Operate—not a generic file browser or chatbot.Agent team and model routingShipsite exposes 14 durable responsibility roles. Runtime stages, deterministic checks, and model choices remain distinguishable.Connections and credentialsHosted planning and managed preview work without third-party setup. Connections are verified before they become active.

Ship and operate

Preview and production deploymentPreview is intentionally easy; production is intentionally gated and evidence-backed.Generated-site runtimeGenerated pages can remain statically deployable while dynamic operations use a project-scoped Shipsite runtime.Search, analytics, and growthShipsite treats growth actions as auditable operations, not as silent automation or guaranteed rankings.

Reference

Credits and billingA user action is billed once as a governed task; internal retries and stage records are supporting evidence, not duplicate charges.Safety and approval boundariesAutomation may prepare evidence and reversible work; consequential external actions require an explicit decision and a real receipt.

What Shipsite does

It connects market research, product and search contracts, design direction, site generation, QA, deployment, search submission, analytics, and iteration in one workspace. The output is not only a rendered page: source, contracts, screenshots, checks, decisions, and release receipts remain attached to the site.

Two ways to start

Create a new site from a keyword or product idea, or import an existing GitHub repository and production URL to establish an auditable baseline without rebuilding it first.

New site: evidence → plan → Owner approval → build → preview → QA → production approval.
Existing site: repository and live-site inspection → baseline → governed changes and releases.

The truth model

A configured button, stored credential, or queued task is not treated as success. Shipsite records a capability as ready only when it has a real API response, artifact, build result, or live endpoint check. Missing providers and blocked actions stay visible instead of being simulated.