Managed Azure, AWS and Google Cloud hosting

Sounds familiar

Hosting nobody is really looking after

Hosting is easy to set up once and forget. The trouble arrives later, and usually all at the same time.

The bill keeps creeping up

Cloud bills drift upward on their own, usually through a test environment nobody switched off or a database still sized for a launch that happened two years ago.

Nobody owns the server

It was set up once and has not been patched since. The login lives with whoever set it up, and they are not around any more.

Renewals get missed

Certificates, domains and operating system support all run out on a date. Without somebody watching, the first sign is the site going down.

Where it runs

Azure, AWS, Google Cloud or DigitalOcean

Most of the cost is decided by how big you make it, not by which provider you pick. If your company has already settled on one, that is where it goes.

Microsoft Azure

A line of business application with a few dozen users runs on Azure App Service with Azure SQL Database. Its APIs and scheduled jobs can sit alongside it in the same account.

Amazon Web Services

The same kind of application on AWS is EC2 and RDS. RDS takes care of the database backups and patching, which leaves less to go wrong.

Google Cloud

Cloud Run suits something that sits idle most of the day, because it costs very little while nobody is using it.

DigitalOcean

Plenty of internal tools run on one DigitalOcean Droplet and never outgrow it. The monthly cost is easy to predict.

Who holds what

Your account, your bill, our work

You see every charge on your own bill. If you ever want us out, you revoke our access and nothing has to move.

TEKTOLOGY Runs it and keeps it patched

Our access, yours to revoke Without moving anything

Your cloud account Opened in your name

Usually on one of these Microsoft Azure Amazon Web Services Google Cloud DigitalOcean

The bill comes to you You can see what it costs

You The account holder

How it goes

Set up once, then looked after

Everything is set up the same way every time and written down, so nothing depends on anybody's memory.

1

Pick where it runs

We match the provider to the size of the job and tell you what it will cost to run before anything is built on it.

2

Open it in your name

The account is yours from the first day and so is the bill. We get the access we need to do the work, and that access is yours to take away.

3

Set it up

Domains, DNS, certificates, backups and monitoring. Alerting that reaches a person rather than a shared mailbox.

4

Keep it running

Operating system patches, runtime and framework upgrades and certificate renewals done well before they expire. We look at the bill from time to time and tell you what can come off it.

Questions about hosting

What people ask first

Do we have to have our own cloud account?

For a company, we would rather you did. It is a cleaner arrangement to end when the accounts were never ours to begin with. Small community groups are the exception, and for those we can hold the account ourselves.

Can you take over hosting somebody else set up?

Yes. It gets the same first look as any system we did not build. What is running, what it costs, whether the backups restore and what has fallen out of support.

Can we take it back and run it ourselves later?

Yes. The accounts are already yours, so nothing has to move. You take our access away, and we hand over the documentation and answer questions for whoever takes it on.

What about servers we already own?

If that is where the software lives, we can look after it there. Not everything needs to move to the cloud, and we will not suggest it just for the sake of a project.

Related services

Tell us what you run and where

What the software is, where it is hosted today and what is bothering you about it. We will come back with questions and an estimate of what it would cost to run properly.

Get in touch Or email sales@tektology.com directly.

Hosting we run, in an account you own