Work Area
Cloud Platforms
We design, move, and run cloud platforms that grow and shrink with demand. We set them up so costs are visible, releases are routine, and recovery is tested, and we tell you when staying where you are is the better choice.
- 1,200+ clients helped
- Building since 2010
- 15 services, one team
- 50+ technologies
At a glance
What we build
We build cloud platforms that run your software on computers rented from a provider, so you can add or remove capacity as needed instead of owning servers.
Problems we solve
Servers in an office are costly to maintain, slow to grow, and a single point of failure when the building or the one person who understands them is unavailable.
Who we serve
Organizations running their own servers, and teams whose cloud bills or reliability have become a worry.
How to choose
Move what benefits from flexibility and reliability first. Keep what is stable, cheap, and tightly controlled where it is.
In practice
Renting capacity instead of owning machines
We set up your software on rented computing services, such as servers, storage, and databases, paid for by use, instead of on machines you own and look after.
This changes how costs work. You pay as you use, so a quiet month costs less. It also changes how risk works, since the provider keeps the hardware running.
The cloud is not automatically cheaper. A badly planned set-up can cost more than the servers it replaced. Planning, monitoring, and review are part of the work.
Your own servers compared with a cloud platform
Before: Your own servers. Bought in advance for peak use; Maintained by one or two people; Down if the building has a problem. After: A cloud platform. Capacity grows and shrinks; Maintained largely by the provider; Copies kept in separate locations.
Before
Your own servers
Fixed capacity that you maintain.
- Bought in advance for peak use
- Maintained by one or two people
- Down if the building has a problem
After
A cloud platform
Rented capacity that follows demand.
- Capacity grows and shrinks
- Maintained largely by the provider
- Copies kept in separate locations
Often built with
The layout
How a cloud platform is arranged
A well-planned platform separates what the public sees from what must stay private.
How a cloud platform is arranged
Layers from top to bottom. Entry; Application; Data; Operations.
- EntryWhere visitors arrive, with protection from misuse.
- ApplicationYour software, running on several machines at once.
- DataDatabases and files, kept private and backed up.
- OperationsMonitoring, alerts, and cost control.
Cost
What drives a cloud bill
| Driver | What it means | How we keep it in check |
|---|---|---|
| Computing | The machines that run your software. | Size them to real use, and switch off what is idle. |
| Storage | Files and databases kept online. | Archive old data to cheaper storage. |
| Data transfer | Information leaving the provider's network. | Place things close together and cache what is reused. |
| Forgotten items | Test systems nobody remembers. | Label everything and review monthly. |
Moving
What to move, and when
Not everything should move at once, or at all.
What are you running today?
Choose this when
Traffic rises and falls, and downtime costs you.
- What you get
- Good first candidates. The platform grows with demand.
- Keep in mind
- Move in stages, and test before switching visitors.
Choose this when
It works, but it is fragile and few people understand it.
- What you get
- Move it as it is, first, and improve later. This reduces risk.
- Keep in mind
- Do not rewrite and move at the same time.
Choose this when
Fixed workload, tight control, and low cost where it is.
- What you get
- Often best left alone, or moved last.
- Keep in mind
- Moving them may add cost and gain little.
A typical example
An application moved off a single server
A typical case is an organization whose application runs on a single server in an office cupboard. When it fails, the one person who understands it must fix it, and the business waits.
A cloud platform could run the application on several machines, keep backups in another location, and alert a team when something goes wrong. A failure would no longer stop everything.
Technology
Under the hood
What we settle early: providers and practices, so nothing surprises your team later.
We work with AWS, Azure, and Google Cloud, and recommend the one that fits your needs, not the one we prefer.
- Infrastructure described in code with Terraform, so it can be reviewed and repeated.
- Separate environments for testing and live use.
- Budgets, alerts, and monthly cost reviews.
Common questions
Questions about cloud platforms
Is the cloud cheaper than our own servers?
Sometimes. It is more flexible, and costs follow use. A steady, predictable workload can be cheaper on owned machines. We compare both honestly.
Can we avoid being locked in to one provider?
Partly. We favor common tools and clear documentation, so moving later is possible, though never free.
Who looks after it once it is live?
That is agreed in advance. You, we, or a mix can monitor it, apply updates, and respond to alerts.
Have a different question?
Tell us what you are weighing up and we will answer it plainly.
Ask a questionAlready a client? Email support@dechytech.com
Tell us what runs where today
Describe your current set-up and what hurts. We will say what to move, what to leave, and roughly what it would cost to run.