Data & APIs
Your database and every API, in one builder.
Rigrid gives every project a real data layer. Store content in built-in collections, connect any REST API, and bind both to your pages without writing a backend.
Built-in collections
A typed database inside every project. Perfect for products, posts, team members, orders and form submissions.
External REST APIs
Keep your data where it lives. Connect your own backend or any third-party service and use it like native data.
Collections
Model any content in minutes.
Define a collection with typed fields and Rigrid handles storage, validation and unique values. Every record gets an id and created and updated timestamps automatically.
13 field types
{
"id": "featured",
"runOn": "server",
"source": {
"kind": "collection",
"collection": "products",
"filter": [
{ "field": "featured", "op": "eq", "value": true },
{ "field": "price", "op": "lte", "value": 30 }
],
"sort": [{ "field": "price", "dir": "asc" }],
"expand": ["category"],
"limit": 8
}
}Queries
Ask for exactly the data you need.
Attach queries to any page, layout or component. Results are ready to bind as soon as the page renders.
Filter
Equals, not equals, greater or less than, in a list, or contains.
Sort and paginate
Sort by any field, set limits up to 1,000 records and page with offsets.
Expand references
Replace reference ids with the full related records in one query.
Server or client
Run on the server for SEO, or in the browser and re-run on demand.
Permissions and forms
Visitors can submit. Only you can see.
Set read, create, update and delete rules per collection. Public content stays readable, while form submissions stay private to your team.
Content
Products, posts, team
Anyone can read. Only your team can create, update or delete.
Submissions
Leads, messages, orders
Anyone can submit. Only your team can read what was sent.
Forms
Straight into your data
Forms validate input, stamp timestamps and ids, and save in one action with success and error handling.
Third-party connectivity
Connect any REST API in four steps.
Payments, inventory, CRM, headless CMS or your own backend. If it speaks REST, Rigrid can read from it and write to it.
01
Add a data source
Set the base URL, headers and auth. Secrets are masked and stay on the server.
02
Define endpoints
Name each endpoint with its method, path, parameters and body.
03
Test it
Call the endpoint from the builder and inspect the real response before using it.
04
Use it anywhere
Load it as a page query, or call it from a button or form with success and error handling.
Read: show products from your API
{
"id": "products",
"runOn": "server",
"source": {
"kind": "endpoint",
"sourceId": "inventory",
"endpointId": "listProducts"
}
}Write: start a checkout on click
{
"type": "callEndpoint",
"sourceId": "payments",
"endpointId": "createCheckout",
"resultVariable": "session",
"onSuccess": [{ "type": "navigate", ... }],
"onError": [{ "type": "toast", ... }]
}Bindings
From response to pixels, no glue code.
Repeat a card for every record, format prices, filter lists from a dropdown and show or hide anything based on data. Collections and APIs work exactly the same way.
data.productsproduct.price | currency('USD')data.products | where('category', vars.category)vars.cart | sum('total')product.stock > 0Put your data on the web.
Connect your first collection or API today, or book a demo and we will map it out with you.

