The Platform
One platform to deploy, secure, and manage all your technology.
400+ open-source databases, applications, AI models, and DevOps tools, deployed into infrastructure you own, then hardened, backed up, updated, and monitored by Tech Citadels. You keep the keys. We do the work.
The Platform
Open-source software, deployed and managed in your environment
We deploy into your cloud or on-premise infrastructure, never ours. Setup, configuration, encryption, backups, updates, and monitoring are handled for you. You keep full ownership.
Deploy in Minutes
Pick any open-source software and deploy instantly. No servers to configure, no Docker files to write, no DevOps expertise required.
Your Environment, Your Data
Everything runs in your cloud account or on your own hardware, never on our servers. No vendor lock-in, full data ownership, total control.
Multi-Cloud and Hybrid
One control plane across AWS, Azure, Google Cloud, Oracle Cloud, OpenShift, and your own datacentre. Run different workloads in different places without running different teams.
One Predictable Bill
Compute, storage, bandwidth, updates, security, and maintenance in a single agreed figure, scoped to what you actually run. No per-seat creep, no surprise line items.
Automated Updates
Always run the latest, most secure versions without lifting a finger. Updates are applied safely in the background.
Encrypted Everything
End-to-end TLS, firewalls, rate limiting, and automated 3-2-1 backups included by default. Your data stays yours.
24/7 Monitoring
Live monitoring with alerts, dedicated VMs with full root access, and support engineers who actually answer.
How it works
Pick a tool
Choose from 400+ open-source databases, apps, AI models, and DevOps tools in our catalog.
We deploy into your cloud
AWS, Azure, Google Cloud, Oracle Cloud, OpenShift, on-premise, or your own VMs. Deployed into infrastructure you own, in the region your regulator requires.
We manage it for you
Hardening, SSL, backups, updates, monitoring, and support, all handled by Tech Citadels, inside your environment.
ISO 27001, SOC 2 & GDPR-aligned practices · Deploy in any region, so data stays where your regulator requires · Encrypted private networking between your services
Service Catalog
400+ open-source tools,
deployed for you
Every deployment includes automated daily backups, free SSL, software updates, OS patches, 24/7 monitoring, and firewall configuration, running in your cloud or on-premise, with full root access for your team.
…and 380+ more. Every tool deployed into your environment and managed by us: we run it, you own it.
Reliability Engineering
Someone is accountable
when it breaks
Managed operations is the easiest thing on a website to claim and the hardest to prove. This is how we run it, what gets agreed before we start, and how you can check we are doing it.
Objectives, not vibes
Every production workload gets an availability target and an error budget. When the budget is healthy we ship changes; when it is burning we stop feature work and spend it on reliability instead.
- Availability target per environment
- Error budget tracked monthly
- Reported to you, not just to us
On-call and escalation
A named engineer is on call around the clock, with a written escalation ladder behind them. Alerts page a human on symptoms your users would notice, not on every metric that moves.
- 24/7 rotation, named not pooled
- Alert on symptoms, not causes
- Escalation ladder to engineering lead
Incidents and postmortems
Severity decides the response and the communication cadence. Every Sev1 and Sev2 gets a blameless postmortem, and you get the same document we do, with the actions and their owners.
- Declared severity drives response
- Status updates on a fixed cadence
- Blameless postmortem shared with you
Observability you can see
Metrics, logs and traces on your infrastructure, in tools you own. Dashboards are yours to open, not a black box we look at on your behalf and summarise in a monthly report.
- Metrics, logs and traces
- Dashboards in your environment
- No black-box reporting
Continuity, tested
Backups that are never restored are not backups. We restore on a schedule and record how long it took, so the recovery objectives below are measured rather than asserted.
- Scheduled restore drills
- Recovery time measured, not assumed
- Documented failover runbooks
Capacity and cost
Headroom reviewed against real growth, instances right-sized against real usage, and spend reported per workload so the bill is explainable rather than a surprise at renewal.
- Headroom against real growth
- Right-sizing against real usage
- Spend attributed per workload
What we agree with you
These four are fixed per environment before an engagement starts, written into your service agreement, then measured on your own infrastructure and reported to you monthly. We set them against your workload rather than publishing one number for everybody.
- Availability target
- The share of the month the service is expected to be up.
- Set per environment, and higher for production than for staging or test.
- Error budget
- The downtime the target allows before it is breached.
- Falls out of the target. Spent it, and feature work stops until it recovers.
- Recovery time objective
- How long a recovery is allowed to take.
- Proven by restore drills on a schedule, so it is measured rather than asserted.
- Recovery point objective
- How much data a recovery is allowed to lose.
- Set by backup frequency, and checked by the same drills.
How we respond
| Severity | Means | What happens | You hear from us |
|---|---|---|---|
| Sev1 | Service down or data at risk | Pages an engineer immediately, day or night | On a fixed cadence until resolved |
| Sev2 | Major function degraded | Pages an engineer, day or night | On a fixed cadence |
| Sev3 | Minor issue, workaround exists | Picked up in business hours | On resolution |
How Engagements Start
Every environment is different,
so we scope rather than quote
What a deployment costs depends on what you run, where it runs and what you want us to take on. Rather than publish a number that will be wrong for you, we will look at it with you and put a real one in writing.
A scoping call
Thirty minutes with an engineer who will be on the work. What you run today, what is hurting, and what you want to be true in six months.
A written proposal
The architecture we would build, what it will cost, and how long it takes. Yours to keep and to take to other suppliers, with no obligation.
A first piece of work
Most engagements start with one workload or one proof of concept, so you can judge us on delivery rather than on a proposal.
An engineer, not a sales rep
The person on the call is the person who would scope and run the work.
Nothing to sign to talk
No obligation and no pressure. If we are not the right fit we will say so.
Get Started
Tell us what you're building.
Whether you need a fully managed open-source stack, a custom product built, or a technology strategy, start the conversation here. An engineer (not a sales rep) will respond.