Who owns the content?

You do, structurally. Every record, upload and end-user account lives in a MongoDB database and storage bucket you supply and control — the platform stores routing data and encrypted connection details, nothing more. The data-handling page lists every collection on both sides. Data ownership in depth →

What does my website actually talk to?

REST APIs. Each schema gets a generated records API with filtering, sorting, pagination and relation expansion — and you can design custom endpoints that run multi-step flows and return exactly the shape your pages need. Custom endpoints →

Can I build API logic without writing server code?

Yes. Endpoints and automations are flows assembled on a visual canvas: query and combine schemas, reshape data with expressions, guard with conditions, call external services and send templated email — with a test run and step-by-step execution logs. How endpoints work →

How do my site's visitors sign in?

Auth schemas give a site registration, login, email verification and password reset out of the box. Signed-in visitors can call endpoints that answer personally — a query filtered to the caller returns only their own records. End-user authentication →

Which frontend stack does it require?

None in particular. The platform is headless: anything that can call an HTTP API works — Next.js, plain HTML, a mobile app. Public endpoints support CORS and response caching, so pages can call them directly from the browser.

Where is the platform hosted, and where is my data?

The platform runs the dashboard and APIs; your data lives wherever your database and bucket live — that's your hosting choice, in your region, under your provider agreement.

Can you migrate my existing site or CMS?

Migration from an existing CMS is a typical engagement — content modelling, imports and custom endpoints built for your site. Get in touch with what you're running. Talk to us →

What does it cost?

Engagements are scoped to the sites you actually run rather than a per-seat grid. Describe your project and we'll come back with a concrete proposal. Pricing →

What happens if I leave?

Your database is already yours. Content sits in plain MongoDB collections in the database you attached, so leaving is pointing your applications at that database — there is no export step and nothing to request.

Is there documentation?

Yes — a guide for every module, written for someone using it for the first time, from getting started through endpoints, auth, media and access control. Read the docs →

Something else? Ask us directly.