Documentation

1. 1Choose an input method. On the Generator page, select Upload Diagram to upload an image, or Describe in Text to type a description.
2. 2Provide your input. Upload a PNG/JPG class diagram or ERD, or type a description such as: A blog with users, posts, comments, and tags. Users can follow each other.
3. 3Generate. Click Generate Schema. The AI streams results into the Tables, Relationships, and RLS Policies tabs in real time.
4. 4Review and use. Switch tabs to review the output. Export as JSON or deploy directly to Supabase (Pro).

Write a natural-language description of your data model. Be specific about entities and how they relate.

Tips for better prompts:

• Name your entities explicitly (not just "users" — say "customers" if that's the intent)
• Mention key relationships ("orders belong to customers", "posts have many tags")
• Call out special columns you need (soft-delete, timestamps, slugs, status enums)
• Mention your domain — e-commerce, SaaS, social network — for richer inference

Upload an image of a class diagram, Entity-Relationship Diagram (ERD), or Use Case diagram. The AI reads the visual structure and extracts entities, attributes, and relationships.

Each table card shows the table name and column count. The full schema (with column names, types, constraints, indexes, and defaults) is included in the JSON export and Supabase deployment.

Every foreign-key relationship is listed with the source table and column, the target table, and the join type. Many-to-many relationships are represented via auto-generated junction tables.

Row Level Security policies control which rows a user can read, insert, update, or delete. Schemavo generates policies tied to auth.uid() so they work with Supabase Auth out of the box.

• Tables with an owner — a user_id column or a foreign key to your users — are private to that user.
• Tables owned through a parent— a task that belongs to a project — follow the parent's owner, up to four levels deep. Junction tables follow the rows they link.
• Tables with no owner at all, such as a list of categories, are treated as shared reference data: signed-in users can read them, and only the service role can change them. Add your own insert, update and delete policies if users should edit them.

Available on all plans. The JSON export contains the full schema definition including tables, columns, relationships, indexes, and RLS policies — ready to be used in your own migration tooling or stored in version control.

1. 1Open the deploy wizard. Click Deploy to Supabase on a project's page, or go to Profile → Push to Supabase → Open push wizard and pick a saved project.
2. 2Enter your Project ID and a personal access token. The Project ID is in your Supabase dashboard under Project Settings → General → Project ID. Create a personal access token (it starts with sbp_) under Account → Access Tokens.
3. 3Test the connection. Schemavo checks that the token can reach your project before anything runs.

After the connection test, the wizard shows the full SQL migration so you can review it — and copy it, if you want to run it yourself. Confirm to run it against your Supabase database.

Every webhook delivers a signed JSON payload via HTTP POST.

{
  "event": "schema.generated",
  "timestamp": "2026-05-24T10:00:00.000Z",
  "data": {
    "projectId": "proj_abc123",
    "tableCount": 5,
    "userId": "user_xyz"
  }
}

Each request includes an X-Schemavo-Signature header — an HMAC-SHA256 hash of the raw body signed with your webhook secret. Verify it to confirm the request came from Schemavo:

const crypto = require('crypto')

function verify(rawBody, signature, secret) {
  const expected = crypto
    .createHmac('sha256', secret)
    .update(rawBody)
    .digest('hex')
  return crypto.timingSafeEqual(
    Buffer.from(expected),
    Buffer.from(signature)
  )
}

Integrations set up before we were renamed from SchemaForge can keep reading X-SchemaForge-Signature — it carries the same value.

Pro is $9 / month or $79 / year (save 27%). Payments are processed by Lemon Squeezy — we never store your card details.

You can cancel your subscription at any time from Profile → Integrations → Billing & invoices → Manage billing.

Cancelling does not remove access immediately. You keep Pro features until the end of your current billing period. After that, your account moves to the Free plan.

You can resume a cancelled subscription at any time before the period ends — no new charge is made until your next renewal date.

Invoices are generated after each billing cycle and available under Profile → Integrations → Billing & invoices. You can download each invoice as a PDF directly from the app.