Choosing a cloud provider for a start-up: a founder’s checklist
A checklist founders can use to assess a cloud provider on cost structure, exit options, support, data location and room to grow.
A start-up chooses a cloud provider based on what the product needs now and what you can move if that changes. Weigh cost structure, export options, support, data location and security options, and test with a real workload before you sign.
Who is it for: Founders and small technical teams who have to choose infrastructure for a product or service for the first time.
Which cloud do you actually mean?
The word cloud has two meanings. In the first it is about files and collaboration: sharing documents, synchronising and backups. In the second it is about infrastructure: servers, databases, object storage and hosting on which your product runs.
This article is about the second meaning. If you need somewhere to share files with your team, that is a different choice with different criteria. You can find those in the guides on cloud storage for small businesses.
Which criteria decide the choice?
A start-up has little time to compare. So begin with the questions that hurt most later if you skip them. These are rarely the technical specifications, but mainly the terms around costs, leaving and support.
Note that the answer differs per provider. A checklist only helps if you put the answers in writing and compare them side by side.
- Cost structure: which items exist (compute, storage, data traffic, support) and which of them grow with usage?
- Exit: can you export all your data and configuration in a common format, and what does the traffic that this causes cost?
- Support: which channels and response times come with your plan, and do you speak to someone with technical knowledge?
- Data location and legal frameworks: where is your data and who manages it? Have this checked legally if you process personal data (GDPR).
- Security: are MFA, role-based access and logging available without an extra contract step?
- Room to grow: are there services for the next stage, such as managed databases or containers, so that you do not have to move?
How do you test a provider before you choose?
A comparison on paper leaves a lot out. A short trial with your own workload gives more certainty than an overview of features.
- Put a slimmed-down version of your product in a test environment.
- Ask a teammate who did not build it to set the environment up again using your documentation.
- Practise a restore from backup and note how long it takes.
- Ask support a realistic question and pay attention to the quality and speed of the answer.
- Export part of your data and check whether you can open it elsewhere.
How do you limit dependence on a single provider?
Being fully independent is rarely realistic for a small team. You can, however, limit the damage of a later move by using open standards, such as containers, an S3-compatible interface for objects and infrastructure that you describe as code.
If you use a service that is specific to one provider, make a deliberate note of why. That way you know later what you need to replace when you switch.
Checklist for choosing a provider
| Criterion | Check question | Why it matters |
|---|---|---|
| Cost structure | Which items grow with usage? | Prevents surprises when traffic or storage increases. |
| Exit | How do I get data and configuration out? | Determines how free you are to switch later. |
| Support | Which response time comes with my plan? | An outage outside office hours hits your customers directly. |
| Data location | Where is the data and who manages it? | Relevant for GDPR and for customers who ask about it. |
| Room to grow | Which services are there for the next stage? | Reduces the need to move later. |
Who is this less suitable for?
- Teams that only need somewhere to share files: look at cloud storage for files, not at infrastructure.
- Products with strict sector requirements: a general checklist is then not enough and you need additional advice.
- Founders without technical knowledge in the team: consider a platform service or a party that takes over management first.
Frequently asked questions
How many providers should I compare?
Two or three is usually enough. Comparing more takes time that you would rather spend on a trial set-up.
Is a European provider mandatory?
No, the law does not require you to choose a particular provider. You do have to comply with the GDPR if you handle personal data. Have a legal check done on what that means for your situation.
Can I run with two providers at the same time?
You can, but it increases the management load. For a small start-up, a good backup outside your main provider is often a more practical first step.
