Universal content management

You're building an app and you need a content model. You need an assets folder and a json doc that tells your code where and what everything is. With Jaina, you can:

Define your model.
Get three doors.

GUI for humans. API for apps. MCP for AI. Define your data types once and Jaina generates the rest — forms, endpoints, SDKs, and an AI-ready tool surface.

Start for free Read the docs

No credit card required
Free tier
Open SDKs

Welcome back

Or continue with

Don't have an account? Create account

Welcome back

One schema

Three interfaces.

Every primitive you define is automatically reflected through three equal access paths. No code generation steps. No glue. No drift.

GUI

for humans

Dynamic forms generated from your schema. Editors, references, file uploads, validation — all wired up automatically.

API

for apps

REST endpoints for every schema. Typed SDKs for TypeScript, C#, and Python. Versioned, documented, batteries included.

MCP

for AI

Model Context Protocol tools for every schema. Claude and other agents read, write, and reason against your data natively.

SchemaUI Forms · API Endpoints · MCP ToolsYour app

Why Jaina

Easily generate your own custom schemas.

Schemas are your custom classes which you author, and create instances of, for your app to consume.

Schemas are first-class

Define types in the GUI, edit them in code, version them in git. Records flow through them without breaking.

Zero boilerplate

No code generation steps. Define a field, it shows up in the editor, the REST API, the MCP tool list, and the typed SDKs.

Auth & multi-tenancy built in

OAuth (Google, GitHub), API tokens scoped to users, Row Level Security policies for every table.

Export to git

Sync packages to disk as model.json + assets. Edit locally, push back. Treat content like code.

Actions & webhooks

Define verbs on your schemas, fire them through any door. Webhooks for record.created, .updated, .deleted with retry logic.

Deployment agnostic

Embed model.json in your app at build time, fetch it from the API at runtime, or sync to disk. Same data, your choice.

Developer experience

Integrate in minutes.

First-party SDKs for the languages your team already uses. Typed clients generated from your schema. CLI for sync, push, pull, and codegen. No glue code.

SDK docs CLI →

$ npm install -g jaina-cli
$ jaina login
$ jaina pull my-game/level-1
$ jaina codegen my-game --lang typescript

// in your claude.json
{
  "mcpServers": {
    "jaina": {
      "type": "http",
      "url": "https://jaina.dev/api/mcp"
    }
  }
}

Ready when you are

Define your first schema.