Introduction
Nimles is a multi-tenant platform on Azure. Each service (identity, content, media, products, commerce, AI and more)
is its own API behind https://api.nimles.com, and every service serves many tenants: each tenant has its own
users, roles and data. You build an app on Nimles by creating a tenant, giving your backend an API client, and calling
the services you need. An API client is an OAuth 2.0 client in your tenant that signs in with the client credentials
grant: you exchange its client id and secret for a short-lived access token.
Built on Nimles
Section titled “Built on Nimles”Nimles is not a demo platform. The same services, through the same APIs, run:
- Product Planner: product management with work items, roadmaps, AI assistance and an MCP server, on Identity, Work Management, AI and Ecommerce subscriptions.
- Gårdsbutiker: a marketplace of Swedish farm shops, each a merchant with its own products, orders and payments, on Directory, CMS, Media, PIM and Ecommerce.
- nimles.com and the shop sites built with the same storefront, with content from the CMS.
- The Nimles portal, where tenants are administered.
The services
Section titled “The services”| Service | Prefix | What it holds | Status |
|---|---|---|---|
| Identity | identity |
Tenants, users, organizations, resource groups, groups, roles, invites, clients (including API clients) | Launch |
| CMS | cms |
Pages, posts, layouts, themes, texts, element templates | Launch |
| Media | media |
Files and folders, served by content.nimles.com |
Launch |
| PIM | pim |
Products, variants, product groups, properties, menus, reviews | Launch |
| Ecommerce | e-commerce |
Orders, quotes, customers, payments, deliveries, discounts, pricelists, stock, subscriptions | Launch |
| AI | ai |
AI agents, chat and chat sessions | Launch |
| Directory | directory |
Profiles (businesses), sites, categories, contacts | Beta |
| Communication | communication |
Beta | |
| CRM | crm |
Relationships, pipelines, deals, forms, messages | Beta |
| LMS | lms |
Courses, subjects, coursework, cohorts | Beta |
| Accounting | accounting |
Books, accounts, records, transactions | Beta |
| Property Management | property-management |
Real estates, vehicles, assets and their records | Beta |
| Work Management | work-management |
Work items, boards, areas, iterations, teams | Beta |
The launch services have an API reference in the sidebar. Every service, beta ones included, is listed in the resources reference, and the MCP server works with all of them.
The developer beta
Section titled “The developer beta”Nimles is in a closed developer beta:
- You sign up in the portal and verify your email address.
- You request developer-beta access from My tenants in the portal, with a line about what you want to build. A Nimles platform administrator grants it, and you get an email when you are in.
- You create tenants of your own (up to three), and API clients in them.
During the beta, APIs can change, and the beta services can change more than the launch ones. The Quickstart walks through all of it.