Prompt it, then open the code.
Describe a backend and vAIF Blueprint generates the schema, the functions and the REST API. Then it is yours: edit it in the real editor, run SQL against the real database, and export the whole thing when you want to leave.
Blueprint
Prompt to schema, functions and APIs.
Blueprint turns a description into a Postgres schema, function source and a generated REST surface — then hands you the editor. It is a starting point you own, not a black box you call.
Describe it
Tables, relations, the endpoints you need. Plain language, in a session you can iterate in.
Review the schema
Tables on a canvas. Change the model before a single row exists, or write the SQL yourself.
Open the editor
Function source in Monaco. Blueprint wrote the first draft; the file is ordinary code from then on.
Function runtimes
JavaScript, TypeScript, Python & more.
Six runtimes, and this is all of them. We do not claim any-language functions, because there is no route that would produce one.
APIs
REST, generated from your schema.
Every table gets endpoints, and every endpoint is testable from the API Explorer with logs and a deployment timeline beside it. The full reference lives in the docs rather than being paraphrased here.
Generated endpoints
CRUD, filtering and pagination derived from the schema — not scaffolding you maintain by hand.
Realtime and storage
Channels, presence and Postgres change feeds, plus multipart uploads and signed URLs.
OpenAPI reference
The spec the SDKs are generated from is the spec the docs publish. One source, no drift.
Export
Take the whole thing with you.
Four targets, all of them real. There is no arbitrary-language export and no lock-in clause that depends on you not asking.
ZIP
The whole generated backend as source you can read, diff and keep.
Docker
A container image you can run anywhere that runs containers.
GitHub
Pushed straight to a repository you own, as a normal commit.
Terraform
Infrastructure for your own GCP or AWS account, applied by you.
SDKs
One published client. 4 not available.
Status comes from the SDK record, which is also what the package pages themselves say. A retracted client is installable and does not work — the sentence on each card is the one printed on its registry page.
TypeScript
@vaif/clientREST core, realtime channels, presence, Postgres CDC, multipart uploads and signed URLs as tree-shakable subpaths.
Python
vaif-clientvaif-client is not functional, and every published version (0.1.0, 0.2.0, 0.2.1 on PyPI) is retracted. 22 of the 27 API paths it calls are not served by the VAIF Studio API. The endpoints it is built around — /db/query, /db/rpc, /ai/chat — are not implemented at all.
Go
github.com/vaifllc/vaif-gogithub.com/vaifllc/vaif-go is not functional, and every published version (v0.1.0, v0.1.1 on the Go module proxy) is retracted. 21 of the 26 API paths it calls are not served by the VAIF Studio API. The endpoints it is built around — /db/*, /ai/chat, /ai/generate/* — are not implemented at all.
Swift
VaifClientVaifClient is not functional, and every published version (0.1.0, 0.1.1 on GitHub) is retracted. 20 of the 25 API paths it calls are not served by the VAIF Studio API. The endpoints it is built around — /db/*, /ai/chat — are not implemented at all.
Dart / Flutter
vaif_clientvaif_client has never been published to pub.dev and is not installable. The client is not functional either: 20 of the 25 API paths it calls are not served by the VAIF Studio API. The endpoints it is built around — /db/*, /ai/chat — are not implemented at all.
Other languages are tracked publicly rather than promised here — see the roadmap.
The docs are the reference.
Quickstarts, the full REST reference, SDK guides and a changelog — versioned, searchable, and generated from the same OpenAPI spec the clients are.