Workspaces and projects
A workspace holds your projects; each project is a self-contained model with its own types, records and team. Nothing leaks between projects.
Collaboration and admin
Who can see what, who is watching it, and how the rest of your stack finds out.
Per-project roles
Owner, admin, data admin and data viewer, assigned per project. Someone can own the model in one project and only read another.
Comments
A discussion thread on the record itself, so the argument about the change sits next to the thing being changed.
Watch, bookmarks and home
Watch a record to hear about it, bookmark the ones you keep returning to, and pin the types you work in to your project home page.
Portfolio home
One page across every project you belong to, for the times the question is bigger than a single project.
Outbound webhooks
Events delivered to your endpoint from a transactional outbox, signed so you can verify them. Your ERP hears about the change without polling for it.
In the APIData API
A server-to-server HTTP API over everything: schema discovery, records, query, search, structures, rollups and change requests, with ETag concurrency and idempotent upsert.
In the APIEmail digests
Approvers get their outstanding change requests by email, so nothing waits three days because nobody opened the app.
Export the whole project
Take the configuration, the records, or the entire project as a bundle you can clone into a new one. Your data is not held hostage by the platform.
In the APIKeep reading
Start free
Want this for your product data?
Spin up a workspace and start building. It only takes a few minutes.