Living software
that evolves with you.

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

intranet.opengea.org
Intrabase dashboard with mail, tasks and events

Software isn't finished the day it ships

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.

Time Cost of each change Traditional framework Intrabase

Three ways to build business software

Traditional frameworkClosed SaaSIntrabase
What you reuseCode and componentsNothing: you use what's thereWhole applications and modules
How it adaptsBy developingBy configuring within the vendor's limitsBy configuring, and developing only what is genuinely new
What a module isA technical componentA feature you don't controlA working application you switch on and off
How it evolvesNew versions to deployWhen and how the vendor decidesThe application already in use grows without being rebuilt
Your dataWherever you put itWith the vendorOne single database, and you can take it with you any time
AIYou integrate itAn add-on assistantAgents 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.

A cycle that never starts over

The traditional model

  1. Design
  2. Develop
  3. Deploy
  4. Maintain

Every significant change starts the cycle again.

The Intrabase model

  1. Configure
  2. Extend
  3. Combine
  4. Automate

The application adapts to new needs without starting over.

Configuration, not projects

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.

Applications

Switch applications on and off per plan, per organization or per account, with no migrations.

Fields

Which fields appear in each list and form, in what order and with what label.

Permissions

Who can do what: roles and permissions per application and per organization.

Languages

All translations are data, not code.

Scheduled tasks

What runs, when and for whom.

Look and feel

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 works inside the system, not next to 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.

workspace.intrabase.app
Claude connector settings: which applications the agent cannot open

Built to be opened up

REST API

Documented with OpenAPI, with an explorer to try it in your browser. It's the same API our own interface uses.

API keys

Per user, scoped by organization and by application. Created and revoked from Preferences.

MCP connector

So AI agents work with real data, under the user's permissions.

PHP 8

Independent modules and automated tests.

api.intrabase.app/v1/explorer
Intrabase REST API explorer
Bash
# 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.

Build your catalogue, not one-off projects

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.

+ New module Shared core Client A Client B Client C

Frequently asked questions

How is Intrabase different from a framework like Laravel or Symfony?
A framework gives you the pieces to build an application. Intrabase is already a platform with working applications (mail, Drive, planner, invoicing, CRM…) and a core that lets you extend and adapt them. You don't start from scratch, and whatever you add can be reused in other installations.
How is it different from an ERP like Odoo?
Both platforms are modular. The difference is the model: Intrabase is made by a cooperative, on its own servers in the EU, with your data exportable at any time and a core we'll release as free software. And it brings in what an ERP usually doesn't: mail, chat, video calls and AI agents on the same database.
Can I develop my own modules?
Today we develop new modules jointly with the partner: they integrate with the other applications and share the same data and permissions. If you only need to connect Intrabase to another system, no module is needed: the API is enough. Once we release the core as free software (first quarter of 2027), partners will be able to develop modules on their own.

Software you won't have to rebuild

Talk to us and we'll show you live how an application that's already running gets extended.