The Shipd Founding Agency Programme

It reads your client's codebase before it writes.

Connect a repository and an agentic explorer walks it the way an engineer would, following imports and reading what matters, then writes an Architecture Brief and indexes the code so the right files reach every generation.

Then choose how closely output hugs their code: style-match for fresh code in their look, vendor to reuse their actual components, or repo to generate against the whole project.

Built one feature at a time, and checked each time.

A one-shot build gives you everything at once and no idea which half works. Feature-by-feature plans the app as real features, builds them in order, and runs a live check after each one before moving on.

The check folds in runtime errors and whether data actually persisted, so a feature that failed is reported as failed, not quietly counted as shipped. For client work, that distinction is the whole ballgame.

A real backend, not a mocked one.

Builds can generate a genuine server and database alongside the frontend, in Node, Python, C# or Java, with your own API routes and schema. Node runs live in the browser preview, and publishes as serverless functions against Postgres.

It is a backend your client owns and can deploy, which is what separates a demo you show them from a project you hand over.

The same panel, in four frameworks.

React · Vue · Svelte · Vanilla JS. TypeScript and Tailwind throughout, with your client’s own components reused when the repo is connected.

A real server, in their language.

Your own API routes and schema, with migrations. Node also runs live in the browser preview and publishes as serverless functions against Postgres.

Run any stack in the cloud

Node, Python, Go, Ruby, PHP, Java, Rust and .NET boot in a sandbox from the repository you connected: the real project with its real dependencies, monorepos included.

Figma and screenshots in

Import a Figma file or drop a screenshot and get a working application. The Shipd Figma plugin also goes the other way, turning an app back into editable layers.

Migrate what exists

Bring in a project from Lovable, Bolt or v0. Connect the repository or upload a ZIP, then carry on from where the client left off.

Ship into their repo

Changes land as a clean delta pull request the client's engineers review and merge. Or export the source as a ZIP. Nothing is trapped in our editor.

Deploy on your accounts

Connect your own Vercel account and deploy to your domains, with environment variables, deploy history and one-click rollback. No Shipd badge on any of it.

Real APIs and scheduled jobs

Generated apps call live third-party services through our server, with no keys in the client, and can run work on a schedule rather than only when someone clicks.

Criteria

Applicants should meet all four.

Not a fit at this stage

Any one of these places a studio outside this intake.

Enterprise requirements are handled separately. Contact us and we will route it properly.

What members provide in return.

The founding rate is not a discount. It is the consideration for early, candid feedback from studios doing the work in production.

These commitments begin only if a studio continues after the evaluation period. A member who withdraws owes nothing.

Everything, in writing, before you apply.

There is no separate agreement to sign and nothing held back for a call. If a term below does not work for your studio, say so in the application.

Is a payment card required to begin?

No. Access is enabled manually and lapses on its own at the end of the evaluation period. There is nothing to cancel and no possibility of an unintended charge.

What happens to our work at the end of the period?

The account returns to the free plan. Projects, versions and connected repositories are retained in full. Nothing is deleted, and paid features simply become unavailable.

Is the evaluation allowance sufficient?

Two million tokens is approximately fifteen complete feature-by-feature builds. If your studio exhausts it inside the period, tell us. That is useful information, and the allowance will be extended.

Can a private client repository be connected?

Yes, through the GitHub App. It requests read access only to the repositories you select and clones over a scoped token. No credentials are pasted into Shipd.

Does our client's code leave their Git host?

It is read to build the architecture brief and the retrieval index that make generation match your client's conventions. Connect with a repository you are permitted to share.

What if we conclude Shipd is not suitable?

The member commitments no longer apply and nothing is owed. We would ask for a short conversation about why, which remains entirely voluntary.