The first customer of the Node Platform is Node.
Before the platform had a signup page it had a tenant: ours. Node Digital's own business - documents, sales pipeline, contract signing, workflow automation, company email, support desk - runs on the same platform, provisioned the same way, behind the same single sign-on, on the same UK hardware that customer tenants use. This page is the honest version of a case study: no invented metrics, just what we actually run.
Why we did it this way
When a small team of engineers runs a hosting platform, the fastest way to find its rough edges is to depend on it. So we made a rule early on: anything we would do for a customer tenant, we do for our own tenant the same way. Same provisioning scripts, same identity model, same backup schedules, same monitoring. No special cases, no side doors.
That rule pays for itself constantly. If single sign-on breaks, we cannot log in to our own CRM. If backups fail, it is our contracts at risk. If an upgrade path is painful, we feel the pain before any customer does. Running the company on the platform is not a marketing exercise; it is our first and harshest test environment.
What we actually run
Our tenant looks like what a customer tenant looks like, because it is one:
Files and documents — Nextcloud holds our company files, shared folders and document collaboration.
Sales and contacts — EspoCRM is our sales pipeline and customer record.
Contract signing — DocuSeal handles our engagement letters and agreements, with the audit trail stored on our own infrastructure.
Workflow automation — n8n glues our internal processes together, from signup events to housekeeping jobs.
Email — our company mail runs on the platform's managed open source mail stack, on our own UK hardware.
Helpdesk — customer support runs through Zammad, so when you email us, the queue the engineers answer from is itself a platform app.
Documentation — our internal runbooks and knowledge base live in BookStack.
AI — our own drafting, summarisation and coding assistance goes through the AI Gateway at api.node.uk, metered and attributed per person and per agent, exactly as customer usage is.
One login, genuinely
Everything above sits behind one single sign-on realm on the platform's Keycloak identity system. One account each, one place to grant or revoke access, and a full audit trail of sign-ins and permission changes. It is the same "one login for your whole business" model every tenant gets - we are just the tenant that has been living with it longest.
Same hardware, same rules
There is no privileged internal infrastructure. Our tenant runs on the same UK-datacentre hardware, the same isolation model, the same ResourceQuota-and-backup discipline as customer tenants, and it appears in the same monitoring and billing pipeline. When we publish an availability badge or a platform claim on this site, we are describing the system our own business depends on.
What this is not
We will not dress this up as a conventional case study. There is no headline percentage, no "300% productivity" claim, and we are obviously not an impartial customer. What it is: evidence that the platform is complete enough to run a real company end to end - files, sales, signing, automation, email, support - and that the people selling it trust it with their own business.
Start where we started - sign up with £15 of free credit and deploy Nextcloud, EspoCRM, DocuSeal or n8n into your own tenant in minutes, or book a meeting and we will plan the rest of your stack as managed setup.
Want the same setup?
Tell us what your business runs on today and an engineer will map it to a tenant - the same kind we run our own company in.