Ulabase

Documentation

How to use your service: store your data, manage your users, and switch on what you need.

Why Ulabase

  • Overview

    Ulabase is a ready backend for web, mobile and AI apps, on a NoSQL database with ready-made features. You can build it with AI agents, and for them.

  • Build with AI agents

    On Ulabase the backend of your app is a folder of setup files. A coding agent such as Claude Code can write and apply it, reading this documentation over MCP.

  • Build for AI agents

    An agent-native app has screens for people and an MCP server for AI agents, on one backend with one set of permissions. Every Ulabase service has both.

  • NoSQL database

    Ulabase stores your data as JSON documents, the shape your app already works with: no tables to design, no migrations, no joins to rebuild an object.

  • Ready-made features

    Accounts, payments, email, webhooks and AI are features of your service that you turn on and configure. Logic of your own runs on services such as Cloudflare Workers or AWS Lambda.

Get started

  • Getting started

    Create a free service, make your first request and connect your web or mobile app with the Kit. It takes about five minutes, and the Free plan needs no card.

  • Starters

    Four complete apps to clone, in React, Angular, Vue and an ecommerce shop, with sign-up and login working and a setup file that configures your service for them.

  • Root user

    Every service has a root user with the widest permission of the service. How to set its password, when to use the Admin JWT, and why your app signs in with its own users.

  • The console

    A tour of the console, where you set up your backend without code: organizations, services, and what each section of a service is for.

  • Plans

    The four plans compared: how much a service carries, backups, support, Enterprise on your MongoDB or ours, and the paths that change on Enterprise.

Your data

  • Collections and documents

    Your app's data is stored in collections of JSON documents: browse, create, edit and delete them from the console, or with the same calls from your app.

  • Indexes

    An index keeps filters and sorts on a field fast as a collection grows; create, inspect and delete indexes from the console.

  • Aggregations

    An aggregation computes reports, counts and grouped data in the database; define it once in the console, test it, and call it from your app by name.

  • Constraints

    A constraint is a rule about a whole collection, such as no negative balance or no double booking; every write that would break it is refused.

  • Schemas

    A schema describes what a document must look like; bind it to a collection and the service refuses every write that does not match.

  • Change streams

    A change stream tells your app the moment a document is inserted, updated or deleted, so the screens update when the data does.

AI New

  • Overview

    Your service can search your data by meaning and let AI agents use it, with the AI providers and keys you choose.

  • AI Keys

    Add the AI providers your service calls to compute vectors and rerank results, each with your own key and default models, checked before they are saved.

  • Auto Embeddings

    Give every document written to a collection a vector for one of its fields, computed by your provider, so you can search the collection by meaning.

  • Auto Chunking

    Split the files uploaded to a bucket into short pieces of text, in a collection you choose, so you can search the content of the files by meaning.

  • MCP

    Every Ulabase service is also an MCP server: AI agents such as Claude can read and change its data, with the same permissions as your app.

Your users

  • Users

    The people and scripts that sign in to your service: create them, give them roles, reset their passwords, and choose what their login token carries.

  • Permissions

    Permissions decide what each role may do in your service: which paths, which methods, and which documents, checked on the server for every request.

  • Tokens

    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.

  • API Keys

    Let your users issue long-lived keys that they can revoke, for an AI agent, a script or an app, with the roles you allow.

  • Sign-up and login

    The service handles registration, email verification, password reset, login with Google and team invitations for your app. You set the URLs and the emails.

Build

  • GraphQL

    Give your app a GraphQL endpoint over your collections with no resolver code: you write a schema and say which collection answers each query.

  • Webhooks

    Call an HTTP endpoint or send an email when a request to your service matches a condition you write, for example a Slack message for every new order.

  • Custom code

    Run your own code on a function platform such as Cloudflare Workers or AWS Lambda, and connect it to your service through the API, webhooks and change streams.

  • Guards

    Block or redirect a request when a rule of yours fails, such as terms not accepted or a lapsed subscription, before the request reaches the data.

  • Origin allowlist

    Only the websites you list may call your service from a browser, so other websites cannot use your users' sessions to call your API.

  • Branding

    Your app's name, color and logo on the sign-in page and in every email your service sends. Three fields, one page, and the emails and the login page follow.

  • Email

    Your app sends email in two ways: the sign-up, password reset, invitation and Stripe emails go out on their own, and an email webhook sends the ones you set up. Each plan has a daily limit, and your own mail server lifts it.

  • Stripe

    Take payments in your app through your own Stripe account, with subscriptions or a product catalog and Stripe's checkout, set up in four steps.

Tools

  • ulabase CLI

    ulabase configures a service from a file in git, the same way from a terminal or a CI pipeline, so every service and environment gets the same setup.

  • Ulabase Kit

    The Ulabase Kit is the client code for your app: sign-up, sign-in, sessions, teams, invitations and payments, for React, Angular, Vue, Next.js and Nuxt.

Reference

  • Users and permissions API

    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.

  • Your own MongoDB

    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.