A voice AI agent for inbound and outbound calls: available 24/7, follows business workflows, performs actions in connec…
A practical guide to CRM–ERP integration: data to synchronise, sources of truth, APIs and webhooks, duplicate protectio…
Hosting is responsible for the hardware being on. Everything above — versions, backups, access, updates and a response at night — belongs to the owner. We take that on.
Discuss the serviceAuditWhat runs, which versions, where backups live and who has access — including forgotten contractors
AccessThe access list is reviewed: extras revoked, key-based login enabled, password login closed
BackupsA schedule, off-server storage and — crucially — a test restore
MonitoringNot just “the server responds”, but the site, the mail and the data exchange as well
UpdatesApplied on a schedule, in an agreed window, with a rollback path
The procedureWhat counts as critical, how fast we respond and who decides at night
An inventory of services, versions, access and backups with a list of risks and priorities.
Web server, database, cache, queues and separation of production from staging.
Schedule, retention, an off-server copy and regular restore verification.
Availability, resources, certificates and key services, alerting the on-call engineer.
Updates, restricted access, brute-force protection and review of suspicious activity.
A procedure with priorities and timings: what counts as critical for your business.
Moving to another provider, adding resources and splitting load as you grow.
What happened over the month, which incidents occurred and what prevents a repeat.
The server, the domain and the hosting are registered to your company. We receive access for the work, actions are recorded, and you can revoke access at any point without losing the infrastructure.
Hosting guarantees the server is powered and the network works. Updates, configuration, backups, mail and incident response are outside that. The difference shows during an outage: the provider will confirm the hardware is fine, and nobody will be there to restore data and bring services back.
Response times are set out before the work starts and depend on what is critical for you: for a store that is taking orders, for a clinic it is booking. Monitoring runs around the clock, and critical checks page the on-call engineer immediately rather than in the morning.
No, we take over other people's too. We start with an audit: you have to know what runs and in what state before accepting responsibility for uptime. If we find something cheaper to rebuild than to repair, we say so immediately with an estimate for both routes.
The infrastructure is yours from the start: server, domain and accounts are registered to the company. On parting we hand over documentation, diagrams and access and, if needed, help the next team get up to speed. We keep no keys to the flat.
Not necessarily. Often it is enough to put order into what already runs. We propose a move when the current environment cannot deliver — no provider-side backups, or resources that no longer match growth. The recommendation always comes with numbers rather than generalities.
