Cloud infrastructure
Cloud bills grow because nobody ever turns anything off. We size infrastructure to the workload, put an alert on the spend, and write down what every resource is for.
Most South African businesses do not need a multi-region architecture, and paying for one is the most common thing we unwind. We start from what the application actually does, then choose the smallest thing that runs it reliably.
Everything is defined as code where the platform allows, so the environment can be rebuilt rather than remembered. That is what makes disaster recovery a procedure instead of a story.
Cost is treated as a first-class constraint: tagged resources, a monthly budget alert, and a quarterly look at what has grown. We bill our time rather than a margin on your cloud spend, so there is no reason for us to want the bill to be bigger.
- AWS or Azure, architected and documented
- Backups, monitoring and cost alerts
- Infrastructure defined as code
Four things arrive, in this order.
Everything below is in the scope by default. If a project does not need one of them, it comes off the quote rather than being quietly left out.
- 01
Architecture
A diagram, a written rationale, and the reasons the cheaper option was or was not chosen.
- 02
The environment
Networking, compute, database and storage, provisioned as code and repeatable.
- 03
Resilience
Backups, a tested restore, and a written recovery procedure with real time estimates in it.
- 04
Cost control
Tagging, budget alerts, and a monthly report in rands rather than in credits.
From the first call to the handover.
You see the work at every stage, on something real. Nothing on this list needs chasing.
- 01
Workload review
What runs, how much of it, and when the peaks are. Guessing here is what causes over-provisioning.
- 02
Design and price
Two options with real monthly costs against each, so the trade-off is yours to make.
- 03
Build
Provisioned as code, deployed to a staging environment first, then promoted.
- 04
Hand over
Access in your organisation's name, the runbook written, and a walkthrough with whoever will hold it.
The things people ask before they commit.
AWS or Azure?
Azure if you are already invested in Microsoft 365 and identity; AWS for most standalone applications. We run both and have no incentive either way.
Do we need the cloud at all?
Not always. For a small marketing site, managed hosting is cheaper and simpler, and we will say so rather than sell the bigger thing.
Who holds the account?
You do. We work inside your organisation with our own named administrator accounts, which you can revoke at any time.
Need cloud infrastructure?
Send through what the business needs and a fixed quote comes back inside two days.
- Office
- Sunninghill, Sandton, 2196
- Hours
- Mon–Fri, 07:00–17:00
- info@bonangtech.com