Documentation

A backend for web, mobile and AI apps: sign-up and login, permissions, payments, live data and an MCP server for agents, on a managed MongoDB.

An app with two interfaces: screens for people and MCP for AI agents, on one backend with one set of permissions. How Ulabase makes it, and how an assistant helps you build it.

Create a free service, get its credentials, make the first request and connect your web or mobile app with the Kit. About five minutes, no card.

Every service has a root user that can do everything: where to set its password, when to use the Admin JWT instead, and why your app never signs in as root.

A tour of the console: organizations, services, and the sections of a service from data to users, integrations and AI. What each one does and where to find it.

What changes between the four plans: capacity, backups, support, Enterprise on your MongoDB or ours, and the paths of system collections that scripts must know about.

The backend of a product catalog on Ulabase, request by request: collections, sample data, a public read permission and queries. Then a starter for the frontend.

Browse, create, edit and delete your app's data from the console, and the same operations over the API: filter, sort, page, and partial updates.

Keep filters and sorts fast as a collection grows: create, inspect and delete MongoDB indexes from the console, with the unique, TTL and full-text patterns.

Reports, counts and grouped data computed by MongoDB: define a pipeline once in the console, test it, and call it from your app by name.

Rules on the whole collection no write can break: no negative balance, no double booking. Written as a pipeline, checked in a transaction on every write.

Refuse a document that does not match: write a JSON Schema once, bind it to a collection, and every write from every client is validated on the server.

Your UI updates when the data does: publish the changes of a collection and your app subscribes over WebSocket with the user's credentials. No polling.

The people and apps that sign in to your service: create them, give them roles, reset passwords, and choose what a login token says about them.

Who may do what in your service, by role: rules with a path, a method and a priority, plus filters that limit a user to their own documents.

Your two credentials as a service owner: a personal access token for ulabase and CI, and a fifteen-minute admin token for a test by hand. Which job wants which.

Let your users issue long-lived, revocable keys for an AI agent, a script or an app, with roles you allow. Turn it on and decide who may issue what.

Registration, email verification, password reset, login with Google and team invitations, done by the service. You set the app name, the URLs and the emails.

Give your app a GraphQL endpoint over your collections without writing resolvers: a schema, a mapping from types to collections, and the endpoint is live.

Call an HTTP endpoint or send an email when a request to your service matches a condition, with the payload shaped by a template: Slack, Mailjet, your backend.

Block or redirect a request that fails a rule of yours, such as terms not accepted or a lapsed subscription, before it reaches the data. Evaluated in order.

Only the websites you list may call your service from a browser. A request from any other Origin is refused, so other sites cannot use your users' sessions.

Verification, reset, invitation and order emails sent for you. How many you can send on each plan, and how to send them from your own address.

Take payments from your app without a payment backend: subscriptions or a product catalog with checkout, billed through your own Stripe account, in four steps.

Configure a service from a file in git: collections, indexes, permissions, features and settings, applied the same way from a terminal or a CI pipeline.

The client side of your backend: sign-up, sign-in, sessions, teams, invitations and payments for React, Angular, Vue, Next.js and Nuxt. One package.

The requests behind the Users and Permissions pages: create a user, grant a role a permission, limit a user to their own documents, hide a field.

Run an Enterprise service on your own MongoDB, on Atlas or self-hosted: the connection string, the network settings to open, and where the service keeps its data.