Multi-tenant platform on Azure
Build on a platform that already runs.
Nimles is a multi-tenant platform on Azure: identity, content, media, commerce, CRM, learning, accounting and AI agents, administered from one portal. Product Planner, Gårdsbutiker and this site run on it.
Built on Nimles
Apps that run on the platform today
Product Planner and the Storefront sites are tenants of the same installation, each with its own users, data and access; the portal is where every tenant is administered.
Product Planner
Product planning for teams, with AI assistance and a native Azure DevOps integration.
Storefront
Company sites, blogs, web shops and marketplaces, server-rendered from one deployment. Gårdsbutiker and this site are Storefront sites.
Portal
Where a tenant is administered: users and access, content, products, orders, CRM, learning, accounting and AI agents.
Services
What the platform provides
Every service is multi-tenant, with its own API and its own section in the portal.
Identity and access
Tenants, organizations, users, roles and API clients. Sign-in with OpenID Connect, and access rules down to the resource group.
Content and media
CMS pages, layouts and posts with drafts and publishing, and a media library served from a public content host.
Products and commerce
Product information, pricelists and stock; carts, checkouts, Stripe payments, orders and order emails.
CRM, learning and accounting
Contacts and deals, courses and classrooms, and accounting, each as a service of its own.
Directory and communication
Profiles and contacts for the businesses a tenant lists, and email sent from the tenant’s own domain.
AI agents and MCP
Tenant agents with chat, and an MCP server that lets AI assistants work with a tenant’s data under its access rules.
How it runs
Many tenants, one installation
One deployment serves every tenant; the services keep each tenant’s data and access apart.
Multi-tenant
Data, users and access are separated per tenant, organization and resource group, in every service.
On Azure
Kubernetes on Azure, Dapr between the services, and workload identity instead of keys for Azure resources.
Event-sourced
Domain-driven services with event sourcing, so every change is on record and projections follow from it.
Open to integrate
REST and GraphQL APIs with OAuth clients, JSON Patch for updates, and an MCP server for AI assistants.
Start in the portal
The portal is where a tenant is run: users and access, content, products, orders, CRM, learning, accounting and AI agents.