Cloud first, ready for on-premises
We avoid tying the application to a single cloud service. Database, file storage and sign-in are configurable rather than hard-wired. The same image can therefore run on your premises or in Azure. We move data and document archives as we would in any other migration.
Containers
Docker is our standard, so test, staging and production environments do not drift apart unnoticed.
Deployment without a night shift
Build pipelines and automated deployment let new versions go live without someone sitting at the server at night.
Authentication
Sign-in through OpenID Connect, connected to Microsoft Entra ID or your existing directory.
External CTO
If no one in-house can take responsibility for architecture decisions, we take on that role for an agreed period: setting up environments, choosing tools and assessing suppliers’ proposals.
Who runs what
In an incident the most expensive minute is the one in which two sides wait for each other.
Building the environment
Responsible
joint
We set the environments up as Docker containers so that test and production do not drift apart, and whether that happens in your own server room or in Azure is your decision.
Deployment
Responsible
crossVault
We build and run the pipeline, and because deploy scripts and build instructions come with the source code we hand over, your people can take it on at any time.
Monitoring
Responsible
to be settled before go-live
Before go-live, we agree who detects outages and who is alerted. If this is left open, the first report often comes from the business department.
Backup and recovery
Responsible
you
Backups are your responsibility unless you explicitly commission us to handle them.
Identity and access
Responsible
joint
We connect sign-in through OpenID Connect to Entra ID or your existing directory; the accounts and groups within it stay in your hands.
System owners
Responsible
you
You name the key users who answer questions and accept changes.
Availability during incidents
Responsible
crossVault
We handle incident reports under the agreed maintenance contract. Which deadlines apply depends on how long your operation can run without the system, and is set out in the maintenance contract.
This split is a proposal, not a standard; we agree it with your IT before the first system goes live.
The technology is rarely the difficult question. Harder is whether your IT team can run it with the staff available. Harder still is making sure someone asks that question before the decision is made.
“You retain the choice between your own server room and Azure.”
Understand your situation. Agree the next steps together.
Tell us what works today and what you would like to change. The first conversation is free and without obligation; afterwards, you receive an initial assessment or possible next steps. You incur costs only when you accept a proposal. For a more detailed business and technical assessment, we agree a separate engagement in advance, with a clear scope and limits on time and cost.
Discuss your project