Intrabase is a modular, open platform designed with sovereignty, privacy and interoperability in mind, built to help shape a safer internet grounded in open standards. Every part has a clear role and can be enabled, replaced or extracted without affecting the rest.
Architecture decisions are often invisible to the customer — but they determine what you'll be able to do tomorrow. These are the four commitments that shape how Intrabase is designed.
Enable only the apps you need. Add functionality as your project grows — without rebuilding anything.
Each module (mail, drive, planner, billing, CRM…) is an independent unit. Enabling and disabling them is instant and requires no migration. You can start with mail and drive and, six months later, add billing and marketing without touching what was already working.
Your data is yours. Export it any time in structured JSON: data, metadata, relationships and full history.
Portability is not an optional feature: it's a guarantee. The export format is documented, stable across versions and preserves every relationship between entities. There's no privileged data that lives only inside Intrabase.
# Full JSON export in a single call curl -H "Authorization: Bearer $TOKEN" \ https://api.intrabase.app/v1/export \ > intrabase-export.json
Automated migrations, syncing with other systems and real-time replication. Documented REST and webhooks.
The Intrabase API is not an add-on: it's the same channel our own interface uses. Anything you can do in the browser, you can do programmatically. OAuth 2.0 and API keys, transparent rate limits and configurable webhooks.
# Receive a webhook when an invoice is paid curl -X POST https://api.intrabase.app/v1/webhooks \ -H "Authorization: Bearer $TOKEN" \ -d '{"event":"invoice.paid","url":"https://mysite.com/hook"}'
All modules share the same data model. An invoice knows its contact, project and related tasks — no syncing, no duplicates.
This is what separates a platform from a collection of apps. In Intrabase, a contact is a contact everywhere: in mail, CRM, billing and tasks. No import, export or reconciliation between tools. Adding a new module automatically inherits the context.
// An invoice natively references its related entities { "invoice_id": "inv_2817", "contact_id": "c_1234", // → same contact as in Mail and CRM "project_id": "prj_42", // → project shared with tasks and events "task_ids": ["t_801", "t_802"] }
30 days free to see how a truly modular platform works.
30-day free trial