What is Nimobase?
Nimobase is the foundation you build your digital product on. What every application has to repeat already comes resolved out of the box: access, companies, payments, documents, AI, notifications and files. You turn on the capabilities you need from the dashboard, without code, or integrate them through the API, the SDKs and MCP — so your effort goes into what makes your product different.
Built-in capabilities
| Functionality | What it solves |
|---|---|
| Access, accounts and companies | Login with a password, JWT with renewal, OAuth 2.0, account recovery, invitations by link, roles and permissions per company, API keys and per-company data isolation. |
| Multichannel notifications | In-app, email, webhook, web push and native push on iOS and Android, switched on or off per user and per notification type. |
| Billing and payments | Plans, prices and plan-included features, subscriptions, charges and payment webhooks decoupled from the provider, and resale plans for your own customers. |
| Documents and taxation | Customers, document types and series with sequential numbers, drafts and immutable issuance, credit notes, proforma→invoice, documents created from charges and a tax catalog per jurisdiction (VAT, GST, sales tax). |
| AI and chat assistants | Multi-provider gateway with your own keys and plan quotas; assistants with skills, knowledge from your own documents, source citations and an embeddable public widget. |
| Files and data | Object storage for the platform and for each company: list, upload, download and share through temporary links. Entity Manager for catalogs and validated instances. |
| Publish and operate | Releases with immutable snapshots, static artifacts, domains and DNS, GitHub and evaluation of existing apps; webhooks, UI analytics, auditing, jobs, backups, feature flags, maintenance and feedback. |
To see the full catalog of capabilities, see Modules.
What the catalog doesn't cover, you model yourself. With the Application DSL you define your own application — roles, forms, views and flows — on top of the data you declare and version in the Entity Manager. And you complete your data management with the object storage, where the files your product produces or receives are stored.