Overview
Software is never finished. Certificates expire, dependencies get security fixes, disks fill, a provider retires a service. Someone has to notice and act, and in a small organisation that someone is usually nobody until a customer calls.
Codeinate takes that job for applications it built, moved, modernized or reviewed. The setup lives in your cloud account, under your name, with Codeinate as an operator you can remove at any time. Monitoring tells Codeinate before it tells your customers, and when it does, the people who answer are the people who know the system.
Questions go straight to the people who did the work. There is no ticket queue. Codeinate's response hours and times are written in the agreement, not in a marketing claim.
What the plan includes
Hosting in your account
The application runs in your AWS, Azure or Google Cloud™ account, or on static hosting with a CDN where that fits. You see the bill, you own the access, you can walk away with everything.
Uptime and error monitoring
External checks that the site answers, error tracking inside the application, and alerts that reach Codeinate. Codeinate tells you what it watches and where the alert goes.
Updates and patches
Dependency and platform updates applied on a schedule, with a test environment first for anything that could change behaviour. Security fixes are not left to wait for the schedule.
Backups that are restored
Automatic backups with a retention rule, and a restore rehearsal on a schedule, because a backup that has never been restored is a hope.
Certificates, domains and DNS
Renewals, DNS changes and the registrar details kept in one documented place, so an expired certificate never takes the site down.
Small changes and a monthly report
An agreed amount of time each month for small changes and questions, and a report in plain words: what happened, what Codeinate changed, what the bill was and what it recommends.
Problems that come up, and what happens next
| The problem | What Codeinate does about it |
|---|---|
| The site went down and the first to know was a customer. | External uptime checks from more than one location, with alerts to Codeinate. You get a message from Codeinate before you get one from a customer. |
| The certificate expired on a Sunday. | Automatic renewal with an expiry check as a second line. Manual certificates are replaced during onboarding. |
| Updates were never applied because they might break something. | A test environment, a schedule and a rollback plan. Updates stop being frightening when they are routine. |
| The hosting login belongs to a former contractor. | Onboarding moves every account, domain and key under your ownership, with Codeinate as a named operator. Access is listed and reviewed in the monthly report. |
| Nobody knows what the monthly cloud bill is for. | The report itemises it. Cost control is part of operating the system, not a separate project. |
How onboarding runs
- 1
Audit
Accounts, access, backups, certificates, monitoring and known issues listed in one document. Gaps are fixed before Codeinate takes responsibility.
- 2
Agreement
What is covered, the response hours and times, what counts as an incident, and the monthly price. In plain words, signed by both sides.
- 3
Operate
Monitoring, updates, backups and the monthly report. Small changes are included up to an agreed amount of time; larger work is quoted.
- 4
Review
Every few months Codeinate reviews the setup, the bill and the risks with you, and adjusts the plan.
When it is down right now and you are not a client yet
Email Codeinate with the URL, what changed last and where it is hosted. If Codeinate can help on a call it will say so immediately; if it cannot, it will say that too and suggest who can.
The first steps are always the same: confirm what is failing from outside, check the last change and the certificate, roll back if there was a release, and get a status message to your customers. Then find the cause, and only then fix it properly.
Ways to keep an application running
| Option | Who notices a problem | Who fixes it | Fits when |
|---|---|---|---|
| Nobody in particular | A customer | Whoever is free | Nothing depends on it |
| Your own staff | Your staff, in working hours | Your staff | You have an operations person |
| Platform as a service | The platform, for platform issues | You, for application issues | The app fits the platform's limits |
| Maintenance plan with the builder | Monitoring, then the builder | The people who know the system | You want one accountable party |
Questions people ask
What is managed maintenance and support?
Managed maintenance and support is when a team runs your application for you: hosting it, monitoring it, applying updates and backups, making small changes and responding to incidents. With Codeinate the application stays in your own cloud account, so you keep ownership and can change operators at any time.
Do you guarantee uptime?
Codeinate puts the response hours and times it commits to in the written agreement, and it reports real uptime every month. Codeinate does not print a percentage on this page, because a number without the agreement behind it is marketing, not a commitment.
Do you support applications you did not build?
Yes, after an audit. Codeinate needs to understand the system well enough to be accountable for it, so onboarding starts with a review and fixes the gaps before the plan begins.
What does the plan cost?
A fixed monthly price agreed after the audit, based on the size and complexity of the setup. The cloud provider's bill is separate and stays in your account.
Can I leave?
Yes, with notice as written in the agreement. Everything is in your account and documented, so leaving means removing Codeinate's access, nothing else.
What counts as an incident?
The agreement defines it: typically the application being unavailable or a core function failing for users. Feature requests and small changes are handled in the included monthly time or quoted separately.





