Quickstart
Start with a no-card trial database.
Sign in, create one trial database, inspect the generated schema, write sample data, and decide what to do next after the product has done real work.
Step 1
Sign in or create a Lovelace account
The public beta gives each eligible account one trial database. No card is required. The trial starts automatically the first time you create a Tabula database through the web app, MCP, REST, or CLI.
The trial includes one database, 1 GB of storage, 10 schema operations, 5,000 data-plane operations, 7 active days, and then 7 read-only days for queries, describes, and exports.
Step 2
Describe the first database
Open Tabula and describe a small database in plain language. For a first pass, use a domain with data you can recognize immediately:
A bookmark manager with URLs, titles, tags, read status, and notesTabula turns that intent into a schema. You should be able to see the proposed tables before you rely on them.
Step 3
Inspect the generated schema
Confirm the first schema has the tables and relationships you expected. In the web app, inspect the database after creation. In an agent host, ask Tabula to describe the database.
Bookmark url: string title: string isRead: boolean notes: string? Tag name: string BookmarkTag bookmarkId -> Bookmark tagId -> TagStep 4
Add and query one record
Write one row so you know the generated schema works for real data. Use safe sample data and placeholder credentials in any CLI, REST, SDK, or MCP configuration.
{ "url": "https://example.com/architecture-notes", "title": "Architecture notes", "tags": [{ "name": "research" }], "isRead": false }Query unread bookmarks and confirm the same shape comes back from the database:
[ { "title": "Architecture notes", "isRead": false, "tags": [{ "name": "research" }] } ]Step 5
Connect an MCP-compatible agent
Add Tabula as an MCP server when you want an agent to create, inspect, query, evolve, or export the database. OAuth handles browser-based sign-in; API keys are for backend automation.
MCP endpoint
https://tabula-api.uselovelace.com/mcpExample JSON config
{ "mcpServers": { "tabula": { "url": "https://tabula-api.uselovelace.com/mcp" } } }Step 6
Decide what happens after the first result
If the schema is close, evolve it with one more instruction. If you want to leave with conventional artifacts, export Prisma, Drizzle, TypeScript, or SQL. If the database should stay writable beyond the trial window, review Launch and Scale after you have inspected the database.
Trial lifecycle at a glance
The trial is read/write for 7 days. From day 7 to day 14, reads, describes, and exports continue while writes are blocked. After day 14, the trial database is deleted. Upgrade or export before that deletion window if the data matters.
Dashboard actions and key management are always free. Only write, raw SQL, fork, provisioning, and schema operations count against your plan. Full billing details
Upgrade details depend on the verified trial-to-paid path. Until then, this quickstart treats paid plans as the continuation step after the first database is working.