Traditional frameworks help you build software faster. Intrabase helps you make it last: applications that are configured, extended and adapted to every new need.

Most of an application's cost comes after it goes live: a new field, a process that changes, a department that joins, a regulation that forces you to redo invoicing. With a traditional framework, every change is a development project. With closed SaaS, every change is a feature request that may never arrive.
Intrabase starts from a different question: not how long it takes to build, but how much it will cost to change five years from now.
| Traditional framework | Closed SaaS | Intrabase | |
|---|---|---|---|
| What you reuse | Code and components | Nothing: you use what's there | Whole applications and modules |
| How it adapts | By developing | By configuring within the vendor's limits | By configuring, and developing only what is genuinely new |
| What a module is | A technical component | A feature you don't control | A working application you switch on and off |
| How it evolves | New versions to deploy | When and how the vendor decides | The application already in use grows without being rebuilt |
| Your data | Wherever you put it | With the vendor | One single database, and you can take it with you any time |
| AI | You integrate it | An add-on assistant | Agents with access to the business and the same permissions as a person |
We're not saying traditional frameworks can't produce modular applications: of course they can. The difference is where the modularity lives. In a framework, the code is modular. In Intrabase, the applications themselves are.
Every significant change starts the cycle again.
The application adapts to new needs without starting over.
Much of what is development in a framework is, in Intrabase, configuration stored in the database. It applies instantly and no new release is needed.
Switch applications on and off per plan, per organization or per account, with no migrations.
Which fields appear in each list and form, in what order and with what label.
Who can do what: roles and permissions per application and per organization.
All translations are data, not code.
What runs, when and for whom.
Each organization's own colours, logo and domain.
When a table or some logic doesn't exist yet, a module gets developed. But that module becomes available to every installation, not just the client who asked for it.
AI agents connect to Intrabase through an open protocol (MCP) and act on behalf of a specific user: they see what that user can see, can only do what that user can do, and everything is logged. It isn't a chatbot bolted onto an ERP: it's one more user, with a name, permissions and a history.
RoadmapWe're working on letting agents propose changes to the application itself (a field, a list, a workflow), which a person with the right permissions reviews and approves before they're applied.

Documented with OpenAPI, with an explorer to try it in your browser. It's the same API our own interface uses.
Per user, scoped by organization and by application. Created and revoked from Preferences.
So AI agents work with real data, under the user's permissions.
Independent modules and automated tests.

# GET /v1/planner_tasks curl -H "Authorization: Bearer $TOKEN" \ https://api.intrabase.app/v1/planner_tasks # POST /v1/mail_contacts curl -X POST https://api.intrabase.app/v1/mail_contacts \ -H "Authorization: Bearer $TOKEN" \ -d '{"full_name":"Anna Garcia","type":"person"}'
RoadmapWe'll release the framework core as free software (AGPL-3.0), without the applications, in the first quarter of 2027.
If you build software for clients, you know every custom project means maintenance forever. With Intrabase, what one client needs and doesn't exist yet becomes a module you can then offer to all the others. We develop new modules together with you: you know the client and their process, and we integrate it into the core so it shares data, permissions and updates with everything else. You manage every installation from a single dashboard, under your own brand, and stop maintaining a different codebase for each client.
RoadmapOnce we release the core as free software (first quarter of 2027), partners will be able to develop and publish modules on their own.
Talk to us and we'll show you live how an application that's already running gets extended.