We set up your cloud, move you onto it, automate your releases, trim the bill and keep it running. Start by grading your own setup: six questions, four grades. Your answers stay on this page.
Answer for your setup today. Yes, not sure and no are all fine. The report card fills in as you go, then the page points to the one or two fixes that fit. It is a guide, not an audit.
1
Have you tested restoring a backup in the last three months?
A backup you have never restored is a hope, not a plan.
Feeds: Backups
2
Do you know what last month's cloud bill was made of?
A bill you cannot read is a bill you cannot cut.
Feeds: Cost
3
Can you release a fix without waiting for one person?
If that person is on leave, does the fix wait?
Feeds: Uptime and Security
4
Is anyone alerted when your site goes down?
Your customers should not be the first to notice.
Feeds: Uptime
5
Do you know who can reach your data?
Think of old staff, vendors and shared passwords.
Feeds: Security
6
Could you move provider if you had to?
Not because you will. It is easier to find out today than in a crisis.
Feeds: Cost and Backups
No answers yet.
What your answers point to
Answer a question and the fixes that fit appear here, each with the reason from your own answers.
A guide, not an audit. This only knows what you tell it, and it cannot see your real setup. A real look at your accounts, bills and servers is the first stage of a move or a tidy-up with us, and your written proposal says what it covers.
Your cloud, graded
0 of 6 answered
Uptime
?
Not checked
Cost
?
Not checked
Security
?
Not checked
Backups
?
Not checked
Nothing checked yet. Each answer fills a dial.
Four fixes, one for each weak spot
Each fix is a service you can hire on its own. The ones your check points to light up. Until you take the check, all four stay plain.
Take the check above and the matching fixes light up here.
Where you run todayOffice servers or one hosting account
1Move one stage
2Run beside the old one
3Switch when you approve
Your cloud accountAWS, Azure or Google Cloud, in your company's name
A way back at every stage
Fix 1Project
Cloud setup and migration
Move to AWS, Azure or Google Cloud without surprises.
Lifts these grades:SecurityBackups
Timeline
In your written proposal
How you can hire us
Project
What it is
We set up your cloud properly, or move what you run today to AWS, Azure or Google Cloud. We move in stages, with the old system running beside the new one until you approve the switch. Your cloud accounts are opened in your company's name.
What you get
A written plan: the order of the move, and a way back for each stage
Cloud accounts in your company's name, with separate test and live areas
Backups set up, and one restored to prove it works
A weekly demo while we move
Documentation, and a handover session for your team
30 days of free fixes after go-live
Good fit if…you run on office servers or one hosting account and want a cloud setup that will not surprise you, or you are starting fresh and want it done properly.
A failed step sends an alertOne step back to the last good version
Fix 2Project
DevOps and CI/CD
Automated testing and deployment for faster, safer releases.
Lifts these grades:UptimeSecurity
Timeline
In your written proposal
How you can hire us
Project
What it is
CI/CD sounds technical. It means every change is tested and released by a machine, not by hand. We set up the steps that test, build and ship your software, so a fix can go live on any day without waiting for one person. If a release goes wrong, you can go back to the last good version.
What you get
Automatic tests that run on every change
A release path to a test copy and then to live
A one-step way back to the last good version
An alert when a release fails
Documentation, so any engineer on your team can release
Good fit if…releases are slow or stressful, wait for one person, or are tested by hand before every release.
The shape of a review. Your own bill sets the real figures.
Your bill, line by line
After the changes you approve
Saved
Needed
Too big
Unused
Badly priced
Right size and price
Fix 3Assessment
Cloud cost optimisation
Find and cut waste in your monthly cloud bill.
Lifts these grades:Cost
Timeline
In your written proposal
How you can hire us
Assessment
What it is
We read your cloud bill line by line and find what is unused, too big or badly priced. You get a ranked list of savings, with the risk of each, and you choose what to act on. Nothing is switched off without your approval.
What you get
Your bill, grouped by what each part pays for
A ranked list of savings, with the risk of each change
Budget alerts, so growth never surprises you
A cost-label plan, so each cost belongs to an app or a team
A short written report you can take to your finance team
Good fit if…your cloud bill keeps growing, or nobody can say what it pays for.
Monitoring, backups, updates and uptime for your apps.
Lifts these grades:UptimeBackups
Timeline
Set up first, then monthly
How you can hire us
Monthly
What it is
We look after your servers and apps every month: monitoring, backups, updates and uptime. When something needs a decision, we ask you first. The accounts and the documentation stay yours.
What you get
Uptime monitoring, with alerts to named people
Scheduled backups, and a restore test each month
Security and software updates in planned windows
A monthly report: what we watched and what we did
Help when something breaks, with a response time agreed in writing
Good fit if…your app has to stay up and nobody on your team is watching it.
Before stage 1 you get a written proposal with scope, timeline and quote, at no cost until you agree. Then every stage ends with something you can see and approve.
Stage 1 of 5 · Move to the cloud
Audit
We list what you run today: apps, databases and files, who uses them, how they connect and what they cost. Access is read-only, so we change nothing.
Why there are no surprisesWe change nothing in this stage.
What you receive
A list of everything that runs today, and who depends on it
A risk list: old software, single points of failure, data that must stay in one country
What can move first, and what should wait
Managed hosting
What we watch every month
This is the list a monthly plan covers. Open an item to see what we do about it. Anything that needs your decision, we ask you first. The exact list for your setup is agreed in writing before we start.
See what an alert does
This is an example. Press the button and the Uptime row goes down, so you can see who is told and what happens next.
ExampleStatus board for a sample app
Sample data, not a real client
What we do about it
We check your site and apps from the outside, on a schedule we agree with you. If something stops answering, a named engineer is alerted and starts on it. You get a short note of what happened and what we changed.
At the end of the month all of this goes into a short report: what we watched, what we did and what needs a decision from you.
What you own, and what we need from you
Yours to keep
Your cloud accounts, in your company's name, with your people as owners
The code, scripts and set-up files we write, in your own accounts
All documentation: what runs where, and how to restore it
Your data and every backup
The logins to every tool and service we set up
What we need from you
1One person who knows how things run today, for a short time in the first week.
2Read-only access to your current hosting or cloud accounts, or exports from them. We sign an NDA first if you ask.
3The last three months of cloud or hosting bills.
4A list of what must not break, and when a short pause is acceptable.
5Someone who can approve each stage, and test your key screens on the day of the switch.
Three ways to start
Pick the one that matches the fix. You get a written proposal with scope, timeline and quote before any work, at no cost until you agree.
Project
Set it up, move it, automate it
For cloud setup and migration, and for DevOps and CI/CD. A fixed scope, from the audit to the handover.
A written proposal with scope, timeline and quote before any work
Weekly demos while we build and move
A backup restored and proven before you switch
Code, accounts and documentation handed over to you
Did not find your answer? Ask us in the box at the bottom.
Should we use AWS, Azure or Google Cloud?
There is no best one for everyone. We compare them for your case: what your software needs, what your team already knows, where your data must stay, and what each costs to run every month. You get our reasons in the written plan. Whichever you choose, the account is in your company's name. Not sure yet? Say so, and we will compare them with you.
How do we keep cloud costs from creeping?
Bills grow when things are left running, sized too big, or when nobody owns the bill. We set budget alerts, label each cost with the app or team it belongs to, and list what is unused. Cloud cost optimisation is an assessment: a short piece of work that ends with a ranked list. On a monthly care plan we read the bill every month. Nothing is switched off without your approval.
Will there be downtime during a move?
We plan to keep it as short as we can. We move in stages and run the old and new systems side by side, then switch over at a time you choose. For some systems a short pause cannot be avoided. If so, the plan says how long and when, and you agree it before we start.
Who holds the admin accounts?
You do. Cloud accounts are opened in your company's name, and your people are the owners. We get named access with limited rights for the time we need it, and you can remove it at any time. We never hold the only key. The logins, the code and the documentation are yours.
Where are our backups, and where does our data live?
In accounts you own. Backups are kept away from the main system, so one failure cannot take both, and we restore one to prove it works. On request, your data stays in the country or region we agree in writing, such as India. We follow India's data protection law (DPDP) and sign a data processing agreement with you. If other rules apply to you, we set out in writing what we do for each. Before we start, we tell you in writing which regions and services we plan to use.
Do you manage our servers after the move?
If you want us to. Managed hosting is a monthly plan: monitoring, backups, updates and uptime, with a report at the end of each month. Or you can run it yourselves with the documentation we hand over. The notice period for ending the monthly plan is agreed in writing before we start, and you keep the accounts, the code and the documentation either way.
How long does each fix take?
Your written proposal shows the timeline for each fix. A move depends on how much you run and how much downtime you can accept. Your written proposal shows the exact timeline before any work starts, at no cost until you agree.
Where the check might lead next
Cloud work often touches these lines too. Each link goes to the matching service.
Tell us what to fix first. A senior engineer replies with how we would approach it, then a written proposal with scope, timeline and quote. No cost until you agree.
Your report card
0 of 6 answered
?UptimeNot checked
?CostNot checked
?SecurityNot checked
?BackupsNot checked
Not filled in yet. Six questions fill it in. Take the check
Quick ideas
Reply within 1 working day · NDA on requestContinue