Skip to content
For developers

Prompt it, then open the code.

Describe a backend and VAIF Verament 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.

VAIF Studio — Develop the future. A luminous blue cube wrapped in a purple orbit.
Schema Functions APIs

Verament

Prompt to schema, functions and APIs.

Verament 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 a full code editor. Verament wrote the first draft; the file is ordinary code from then on.

Function runtimes

JavaScript, TypeScript, Python & more.

Choose the runtime for each function. These six are available.

JavaScript
compiled for Node.js 20 or 22, runs on Node.js 22
TypeScript
Compiled for you
Python
3.11
Go
1.21
Deno
TypeScript or JavaScript
Bun
TypeScript or JavaScript

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.

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 spec per project

Each project's generated endpoints come with an OpenAPI spec built from its schema. Explore it, mock it, or generate your own client from it.

Export

Take the whole thing with you.

Export the generated backend in any of these four forms, whenever you want.

ZIP

The whole generated backend as source you can read, diff and keep.

Docker

A Dockerfile and compose file generated for your backend, ready to build and run anywhere containers do.

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

Eight current clients, not yet released.

Client libraries for the VAIF API, and where each one stands.

TypeScript

@vaifstudio/client
Not on npm yet

REST core, realtime channels, presence and Postgres CDC, plus multipart uploads and signed URLs as tree-shakable ./storage subpaths. 4.0.0 is not on npm yet.

Python

vaifstudio
Not on PyPI yet

vaifstudio 1.0.0 is the current client. It is not on PyPI yet. The hosted API (https://api.vaif.studio) and console are not available yet. It was formerly published as vaif-client; those PyPI releases (0.1.0, 0.2.0, 0.2.1) are the previous client and should not be installed.

Go

github.com/vaifstudio/vaif-go
Not tagged yet

github.com/vaifstudio/vaif-go 1.0.0 is the current client. It has not been tagged yet. The hosted API (https://api.vaif.studio) and console are not available yet. The earlier tags (v0.1.0, v0.1.1) are retracted.

Swift

VaifClient
Not tagged yet

VaifClient 1.0.0 is the current client. It has not been tagged yet. The hosted API (https://api.vaif.studio) and console are not available yet. The earlier tags (0.1.0, 0.1.1) are retracted.

Dart / Flutter

vaif_client
Not on pub.dev yet

vaif_client 1.0.0 is the current client. It is not on pub.dev yet. The hosted API (https://api.vaif.studio) and console are not available yet.

Java

studio.vaif:vaif-java
Not on Maven Central yet

studio.vaif:vaif-java 1.0.0 is the current client. It is not on Maven Central yet. The hosted API (https://api.vaif.studio) and console are not available yet.

C# / .NET

Vaif.Client
Not on NuGet yet

Vaif.Client 1.0.0 is the current client. It is not on NuGet yet. The hosted API (https://api.vaif.studio) and console are not available yet.

Kotlin

studio.vaif:vaif-kotlin
Not on Maven Central yet

studio.vaif:vaif-kotlin 1.0.0 is the current client. It is not on Maven Central yet. The hosted API (https://api.vaif.studio) and console are not available yet.

The docs are the reference.

Quickstarts, the REST reference generated from the same OpenAPI spec as the clients, SDK guides and a changelog, all searchable.