IT DigiApp
We build and run the environment your application lives in
Most teams can write the application. What stops them is everything underneath it — the database, the secrets, the certificates, the backups, the alerting at two in the morning. IT DigiApp provisions that as a managed environment, at the size the work actually needs, and runs it.
The tiers
Four environments, and you can run more than one
These are not steps on a ladder you climb once. Most teams end up running two at the same time — a staging environment beside production, so changes can be proven somewhere real before they reach the people who depend on them.
-
POC
For an idea that has not been proven yet
$22per month
A front-end application and a database, with a secret store and a managed identity. Single region, no redundancy. Deliberately disposable — it has an expiry date and gets torn down rather than quietly billed forever.
- Application hosting and a managed database
- Secrets held properly from the first day, not retrofitted later
- Its own isolated resource group
-
Staging
For work that needs somewhere real to land
$59per month
Everything in POC, plus a proper address and a deployment path. This tier is not about size — it is about being reachable, deployable and safe to break.
- Custom domain and certificate
- A deployment pipeline target
- Seeded non-production data
-
Prod
For an application people depend on
$99per month
Production sizing, redundancy where the platform offers it, and the operational layer that turns an environment into a service.
- Automated backups with a stated retention
- Monitoring and alerting with a real destination
- Web application firewall in front of it
-
Prod+
For when downtime has a number attached to it
$299per month
Everything in Prod, at a larger size, with the resilience written into an agreement rather than described in a diagram. This is the tier where recovery targets stop being aspirations.
- Multi-region, with a stated recovery point and recovery time
- Private networking — the database is not reachable from the internet
- A service level and a support response time, in writing
Prices are per environment, per month, and you can run more than one. Larger applications may need sizing above the standard tier — if yours does, we will tell you before you buy rather than after.
One shape, four sizes
Every tier is the same architecture with different dials. Moving up is a change of size, never a rebuild — so the environment you start on is the environment you grow.
Isolated from day one
Every environment gets its own resource group, its own secret store and its own identity. Nothing is shared with another customer, at any tier, including the throwaway ones.
Run, not just handed over
Production tiers come with backups, monitoring and someone to call. An environment nobody watches is a liability wearing the costume of an asset.
Choosing
Where you start depends on what you already know
The idea is still unproven
Start at POC. Get something running that real people can use, cheaply, and find out whether it earns a bigger environment. Most first engagements begin here.
You already know the idea is solid
Go straight to Staging. There is no value in proving something you have already proven. Skip the throwaway tier and start on an environment you can deploy to properly.
You are moving something that already runs
Start at Prod or Prod+. A migration is not an experiment. The target environment has to match what the application already relies on from the first day it carries traffic.
At every tier
Things we do not treat as upgrades
Some things are cheap to include at the start and expensive to add later. We do not sell those as a higher tier — they are in the smallest environment we build.
Secrets held properly
A dedicated secret store and a managed identity from the first environment. Retrofitting this later changes how every component authenticates — configuration, deployment and local development all at once. It costs almost nothing to do at the start.
Isolation you can prove
One resource group per environment, named by convention. It is what makes clean teardown, honest cost attribution and a contained blast radius possible at all. Added after the fact, it is a migration.
The same architecture at every size
The difference between POC and Prod+ is sizing, redundancy and count — never a different set of parts. That is what makes moving up a change of configuration instead of a rebuild, and it is a decision made once, at the beginning, on your behalf.
Start with a conversation about the application
We will tell you which tier fits, what it will cost, and what we would do first. If the honest answer is that you do not need us yet, we will say that too.