Solutions
Four services, and what each one deliberately excludes
Every engagement uses two or three of these. Each page states plainly what is out of scope, because that is the part most proposals leave for you to discover later.
Deployment & configuration
Design, deploy and configure an open-source platform against how your organisation actually works.
How it worksData migration
Profiling, mapping, dry runs at production volume, and reconciliation reporting at every stage.
How it worksManaged hosting
Patching, backups with tested restores, monitoring and upgrades — in your cloud account or ours.
How it worksSupport & maintenance
Annual support against a deployed platform, with response targets and a quarterly review.
How it worksHow they combine
A typical engagement
Most clients start with deployment and migration, then move onto hosting and support once they are live.
Months 1–4
Deployment & configuration
Discovery, environments, configuration, UAT.
Months 2–5
Data migration
Runs alongside the build. Profiling first, then dry runs.
From go-live
Managed hosting
Patching, backups with tested restores, monitoring.
From go-live
Support & maintenance
Named contacts, response targets, quarterly review.
You are not obliged to take all four. Several clients take deployment and migration, then run the platform themselves with the runbooks we hand over.
Talk to someone who will tell you if it is a bad fit
A scoping conversation, not a sales call. We will tell you what the platform does today, what it would cost, and where the risk sits.