Developer platform · Closed beta
The multi‑tenant backend for your SaaS.
Identity, content, media, products, commerce and AI behind one API, on Azure. Create a tenant, give your backend an API client and call the services you need. The same services run Product Planner and Gårdsbutiker.
# 1. A token for your tenant (client_credentials)
TOKEN=$(curl -s \
"https://auth.nimles.com/tenant/$TENANT_ID/connect/token" \
-d grant_type=client_credentials -d scope=nimles.user \
--data-urlencode "client_id=$CLIENT_ID" \
--data-urlencode "client_secret=$CLIENT_SECRET" \
| jq -r .access_token)
# 2. Any service, one URL scheme: here the tenant's pages
curl -s -H "Authorization: Bearer $TOKEN" \
"https://api.nimles.com/cms/api/tenant/$TENANT_ID/Pages"How it works
From sign-up to your first call
The developer beta is closed: you sign up, request access in the portal, a platform administrator grants it, and you are minutes from your first request. The quickstart in the docs walks through every step, in bash and PowerShell.
Step 1
Sign up
Create your account in the Nimles portal and verify your email address.
Step 2
Get beta access
Under My tenants in the portal, write a line about what you want to build and request access. A Nimles platform administrator grants it, and you get an email when you are in.
Step 3
Create a tenant
Under My tenants, create a tenant. You become its Owner, and it gets a Default resource group where your content lives. You can have up to three.
Step 4
Create an API client, call the API
In the tenant’s Developer section, create an API client with a role; its secret is shown once. Exchange its client id and secret for a short-lived token at auth.nimles.com and call any service on api.nimles.com.
Services
Six services with a full API reference, seven more in beta
Every service is multi-tenant and follows the same conventions: one URL scheme, one token, one response envelope and JSON Patch for changes. REST lists answer everything at once; CMS, PIM, Ecommerce and Directory also take paged, filtered reads over GraphQL.
Identity
Users, organizations, resource groups, roles and API clients. Sign-in with OpenID Connect, and access like Azure RBAC, down to the resource group.
CMS
Pages, posts, layouts and themes, with drafts and publishing, through REST and GraphQL.
Media
Files and folders, image transforms and signed URLs, served from content.nimles.com.
PIM
Products, variants, product groups and properties, with publishing.
Ecommerce
Orders, quotes, customers, payments, deliveries, discounts, pricelists, stock and subscriptions.
AI and MCP
AI agents and chat over the API, and an MCP server that lets assistants work in a tenant as the signed-in user.
In beta
Seven more services with the same conventions and the same MCP server. They are listed in the resources reference and may still change during the beta.
directory communication crm lms accounting property-management work-management
Built on Nimles
The proof: products that run on it today
Nimles is not a demo platform. The same services, through the same APIs, run these products. This page is itself a page in the CMS.
Product Planner
Product management with work items, roadmaps, AI assistance and a native Azure DevOps integration. Its plans are Ecommerce subscriptions.
Runs on identity directory cms media work-management ai e-commerce
Gårdsbutiker
A marketplace of Swedish farm shops. Every shop is a merchant with its own products, orders and payments, on one storefront.
Runs on identity directory cms media pim e-commerce
The storefront
One server-rendered deployment that serves company sites, blogs, web shops and marketplaces as tenants: nimles.com, Cloud Technologies and Gårdsbutiker are each a tenant of it.
Runs on cms media directory pim e-commerce identity
For AI-era developers
Your tenant, in your AI assistant
The hosted MCP server at mcp.nimles.com lets Claude Code, VS Code and other MCP clients work with your tenants: look up and change content, products and orders, upload media, publish pages. You sign in as yourself, and every call runs with your own roles. The server never has more rights than you.
# Claude Code
claude mcp add --transport http nimles \
https://mcp.nimles.com/mcp
# VS Code, or any MCP client with Streamable HTTP and OAuth
# .vscode/mcp.json → "nimles": { "type": "http",
# "url": "https://mcp.nimles.com/mcp" }Start building in the beta
Sign up in the portal and request access from My tenants. A platform administrator grants developer-beta access; with it you can create up to three tenants of your own, and the docs take you from there to your first page in about ten minutes.