Everything in the core — and how real each part is
Every line carries the same status label as our products, stories and security page. “Used by” means a product of ours runs on it today.
Statuses as of 22 October 2026.
Identity & access
Who can sign in, how, and what they may do.
Sign-in, sessions & profiles
Password sign-in, session handling, user management, self-service profiles and login history.
Multi-factor authentication
Authenticator-app codes with backup codes, and a per-tenant switch to require them.
Token security
Short-lived access tokens, one-time refresh rotation, a revocation list and bulk session revocation.
Roles, permissions & policies
Role-based access on a shared permission catalogue, an attribute policy engine (owner-only, roles, time and IP ranges, deny-overrides) and scoped permission delegation.
Invites & public onboarding
Admin invites, public invite links, and a self-serve onboarding flow with an activation checklist.
Exercised by FixerJi’s staff and professional invites and by the end-to-end test suite.SAML single sign-on
Per-tenant identity-provider setup, with signed-assertion checks for wrapping, audience, issuer, recipient and replay.
Hardened and tested in July 2026; not yet verified with a customer’s own identity provider.OIDC & social sign-in
OpenID Connect per tenant, plus Google and GitHub sign-in.
The endpoints are built; they need provider credentials before they can run.Magic links & phone codes
Email magic links and one-time phone codes.
Magic links are built; phone codes need an SMS provider, and none is connected.SCIM 2.0 provisioning
Automatic user provisioning from an identity provider, authenticated by a per-tenant bearer token.
Users can be created, read, updated, deleted and listed, and that route is live through the gateway. Still missing: PATCH, Groups, automated tests, and a gateway route for creating the bearer token an identity provider needs.Support impersonation
Time-boxed, audited sessions as a user, behind step-up authentication.
GDPR erasure
Two-step, token-confirmed erasure that anonymises every identity field and records completion.
Covered by automated tests.Tenancy & control plane
One platform, many isolated businesses — and the controls to run them.
Tenant lifecycle & policies
Create, suspend and reinstate tenants, with members, roles and per-tenant policies for MFA, passwords and sessions.
Application registry
Register the applications that belong to a tenant.
API keys & webhooks
Machine-to-machine API keys and tenant webhooks signed with HMAC.
Data export & scheduled purge
Export a tenant’s data, and purge it on a schedule when a tenant leaves.
Billing, payments & money
Plans, payments, ledgers and wallets, built for more than one payment provider.
Plans, subscriptions & trials
Versioned plans; subscribe, change and cancel with proration; trials and tenant plan tiers.
Every tenant’s plan tier and API quota runs through it.Usage metering & quotas
Per-tenant usage metering, quotas, and an early-warning signal before a limit is hit.
Invoices, ledger & billing portal
Invoices, a double-entry ledger with a trial balance, and a self-serve portal for invoices and payment methods.
Payments: Razorpay, Stripe & manual
A registry of payment providers with saved payment methods, hosted checkout and webhooks.
Razorpay test-mode checkout ran end to end on 14 October 2026. GreenLeaf used a mock provider, and Stripe is built but not exercised.Refunds, disputes & adjustments
Refund and dispute handling, and manual adjustments.
Coupons, tax rules & revenue recognition
Fixed and percentage coupons, tax rules, and ASC 606 revenue recognition.
Reconciliation & event replay
Reconcile payments against providers, and replay billing events.
Wallet & payment holds
Multi-currency stored value with credit, debit and transfer, and holds that are later released or captured.
FixerJi’s cancellation credit is a wallet credit, as in the 14 October 2026 run.Engagement
Reaching people: notifications and real-time chat.
Notifications
Email, in-app, push and webhook channels, with per-channel sender settings, delivery webhooks and an operator retry queue.
Push is proven (3.6 seconds in the 14 October 2026 run). Email goes to a local mail sink until an SMTP provider is configured.SMS & WhatsApp
Text and WhatsApp delivery.
The notification service has the channel, but no provider is connected: SMS messages are logged, not sent.Real-time chat
WebSocket chat channels with message history, search and unread tracking.
FixerJi’s private booking chats run on it.Product intelligence
Know what users do, and change behaviour without a redeploy.
Event analytics
Event tracking and queries, cohort retention, funnels, a live event stream and CSV export.
Smoke-tested on 22 October 2026: starts clean and records platform events from the event bus. Not running on the live platform today.A/B experiments
Experiment assignment and variants, alongside analytics.
Ships inside the analytics service, which is not running on the live platform today.Feature flags
Platform defaults with per-tenant overrides, changed without a redeploy.
Operational toggles: boolean, with per-tenant overrides. No segment targeting or multivariate flags.Localisation
A shared service for translation resources.
Workflow & events
Long-running processes, an append-only audit trail and durable queues.
Events & audit trail
A transactional outbox publishes domain events to Kafka with dead-letter replay, feeding a searchable, append-only audit store.
FixerJi’s booking events feed the tenant audit log.Event-driven workflow rules
Rules that react to platform events.
Durable workflows & sagas
A state machine for long-running processes, with step idempotency, templates, reverse-order compensation and an operator control plane.
Built for the platform’s own onboarding, subscription and team flows. Happy paths are demonstrated; automated test coverage is thin.Plugin registry
Register and manage extensions to the platform.
Durable job queue
Enqueue, poll and retry background jobs.
Running and tested; no product uses it yet.Business operations
The sales pipeline behind a business.
CRM
Leads, opportunities, accounts, contacts and activities, with a public lead-intake route.
API only — there is no CRM screen yet. It captures this site’s own lead forms.Platform foundation
The edge, storage and instrumentation everything else stands on.
Zero-trust gateway
Validates the token once at the edge, forwards signed identity headers, and enforces rate limits and per-tenant quotas.
Tenant document store
Tenant-scoped JSON collections and items.
Smoke-tested on 22 October 2026: starts clean and serves its API.Media storage
Tenant-scoped object storage with usage tracking.
White Owl’s payment proofs are stored here.Tracing, metrics & logs
Every service emits structured logs, traces and metrics.
The dashboards (Jaeger, Prometheus, Grafana, Loki) are an optional tier that is not running on the live platform today.One Zero-Trust edge, a fleet of services
Your product, web app and SDKs talk to a single gateway. The platform validates once, signs identity headers, and the services handle the rest.
A real operator console, not a black box
Every tenant, user, subscription and audit event is visible and controllable — the same operational surface MergeMind Commerce runs on.
MergeMind
Dashboard
Tenants
Users & roles
Billing
Audit log
Settings
Operator dashboard
Active tenants
128
+6 this week
MRR
$42.6k
+4.1%
Events today
18.2k
audited
Tenants
Acme Field Services
Scale
Northwind Logistics
Startup
Globex HR
Developer
Initech Ops
Startup
One integrated core, not five point solutions
Auth0 for identity, Stripe for billing, LaunchDarkly for flags, a queue, an audit tool — each is a contract, an integration and a seam. MergeMind gives you all of it, designed together.
Designed together
Identity, tenancy, billing and authorization share one model — no glue code between vendors.
One Zero-Trust edge
A single signed-header gateway secures every service; downstream code never parses a JWT.
One API, one bill
One platform to learn and operate, one consistent API across every capability.
We didn't start with a platform. We extracted one.
MergeMind began with a commerce product. As we built it, we kept pulling the horizontal concerns — identity, tenancy, billing, audit, workflows — into reusable services. Those services became the core. Then we built a services marketplace, a learning engine and a finance product on the same core, and every gap they hit became a platform capability.