Infrastructure for your company, from audit to 24/7 operation
CloudHosting builds and runs IT infrastructure for companies: dedicated servers, private clouds, colocation and private networks, all in our own Tier 3+ data centre in Riga and on our own network. We analyse what you have, design what you need, migrate without surprises and then operate it with monitoring around the clock. It fits companies that have outgrown a single server but do not want to run a server room of their own.
What we build
Not plans from a price list. Each project is sized from your workload, availability needs and budget, on hardware we own and operate.
Dedicated server platforms
One server or a fleet: hardware picked for the workload, installed in our racks, wired into our network and handed over ready for production.
Private clouds
A virtualization platform on dedicated hardware that only your company uses. Your own pool of CPU, RAM and storage, isolated from other clients.
Hybrid setups
Your own equipment in our colocation racks combined with our servers and cloud. One network, one support team, one bill.
Private networks
VLAN segmentation, private interconnects between your servers and offices, site-to-site VPN over IPsec or WireGuard, public IPv4 and IPv6.
Backup and disaster recovery
Backup schemes with recovery targets agreed in writing: how much data you can lose (RPO) and how fast you are back (RTO), tested, not assumed.
Monitoring and administration
Our engineers watch your systems around the clock, apply updates, react to incidents and stay available as your ongoing IT operations team.
How a project runs
Four stages, each with a concrete result. You see the design and the numbers before anything is bought or moved.
- 1
Audit and analysis
We inventory your current servers, services, network and dependencies, and find what limits performance, availability or compliance today.
- 2
Design
You get a written architecture: hardware, network scheme, backup and recovery targets, monitoring scope and a fixed monthly cost.
- 3
Migration
We move services in agreed windows with a rollback plan for every step. Data is synchronised in advance so the cutover downtime is minutes, not days.
- 4
Operation
The platform goes under 24/7 monitoring. Updates, incidents, capacity and backups become our job, with response times fixed in the contract.
Our own network underneath it
The infrastructure sits on a network we run ourselves, not on rented virtual machines in someone else's cloud.
Own ASN and BGP
We announce our address space over BGP with redundant upstreams, and we register and route IPv4, IPv6 and AS numbers for clients through RIPE.
Private connectivity
Dedicated links between your racks, servers and offices that never touch the public internet, from a VLAN in one rack to links between sites.
Site-to-site VPN
Encrypted tunnels between our data centre and your offices or other providers, on IPsec or WireGuard, with routing our engineers maintain.
Tier 3+ data centre
Our own facility in Riga with N+1 power, redundant cooling and 24/7 physical security, plus capacity in Naaldwijk in the Netherlands.
Availability and recovery, in numbers
Every availability promise costs money, so we design to the numbers you actually need instead of selling the maximum.
RPO: how much data you can lose
If your RPO is one hour, backups or replication run at least hourly. We agree the number per system: a database usually needs minutes, an archive can live with a day.
RTO: how fast you are back
Recovery time defines the design: restore from backup, a standby server, or an automatic failover pair. We state the target in the contract and test it with you.
High availability where it pays
Duplicated servers, storage and network paths for the systems that truly cannot stop, and honest advice where a good backup is the more sensible spend.
Compliance and control
Your data stays in the European Union, on hardware you can point at, under rules you can show an auditor.
GDPR by location
Data lives in our data centre in Riga, in the EU. We sign a data processing agreement and can host and process everything without a non-EU transfer.
NIS2 support
For companies covered by NIS2 we act as the responsible IT role: documentation, incident handling and reporting duties handled by our engineers.
Access and audit
Access to your systems is named, logged and revocable. For audits we provide the network diagrams, backup reports and change history you need.
Typical projects
What this looks like in practice. Scale and components differ, the approach does not.
Manufacturing company
ERP and factory systems
ERP moved from an office server room to a dedicated platform with hourly backups, a standby copy and a VPN to the factory network.
IT company
SaaS production platform
Production on dedicated servers with a private VLAN, staging on VPS, deployment access for the team and 24/7 monitoring with agreed response times.
Retail chain
Shops, tills and head office
Central systems in our data centre, site-to-site VPN to every shop, own equipment in colocation and one support contract for all of it.
Engineering guides
Written by the same engineers who run these platforms.
FAQ
How is this different from just renting a VPS or a dedicated server?
A VPS or a dedicated server is a product: you order it, you run it. Enterprise infrastructure is a project: our engineers analyse your current systems, design the platform, move your services onto it and then operate it under monitoring. You get an architecture matched to your workload, written recovery targets and a team responsible for keeping it running, not just hardware in a rack.
Do we have to move everything to your data centre?
No. Hybrid setups are common: your own equipment in our colocation racks, our dedicated servers for the heavy workloads, VPS for smaller services, and private links or VPN tunnels to systems that stay in your office or with another provider. We design around what already works for you and only move what gains from moving. The result still behaves as one network with one support team.
How do you migrate without breaking things?
Every migration starts with an inventory and a written plan: what moves, in which order, in which service window, and how each step rolls back if something goes wrong. Data is synchronised to the new platform in advance, so the actual cutover is a short, controlled switch rather than a long copy. We schedule cutovers outside your business hours and stay on the line until your team confirms everything works.
What do RPO and RTO mean in practice?
RPO, recovery point objective, is how much recent data you can afford to lose: an RPO of one hour means backups or replication run at least hourly. RTO, recovery time objective, is how fast the system must be back after a failure. The numbers drive the design and the price: minutes of RTO need a standby server or automatic failover, while a few hours can be covered by a tested restore from backup. We agree both per system and put them in the contract.
Where is our data physically stored?
In our own Tier 3+ data centre in Riga, Latvia, inside the European Union, with additional capacity in Naaldwijk in the Netherlands. The servers sit in racks we own and operate, on our own network. For GDPR purposes that means your data can be hosted and processed entirely within the EU, and we sign a data processing agreement that states exactly where it lives and who has access.
Can you take over infrastructure that another provider or our own admin built?
Yes, that is a normal starting point. We begin with an audit: we document what exists, fix the risky parts first, and only then propose changes. You do not need to plan a rebuild to hand over operations. If the current setup is sound, we put it under monitoring and backups and simply run it. Where it limits you, we show the redesign with numbers and you decide the pace.
What does 24/7 monitoring actually cover?
Availability and health of the servers, services and network links we agreed to watch: load, disks, backups completing, certificates expiring, and the reachability of your key services. Alerts go to our on-duty engineers, not to a mailbox nobody reads at night. Reaction and escalation times are fixed in the contract, and you get access to the same monitoring so you see what we see.
What does a project like this cost?
It depends on hardware, availability targets and how much operation you hand over, so there is no honest price list. The process protects you instead: after the audit you receive a design with a fixed monthly figure before anything is ordered. As a rough anchor, small setups start around the cost of a few dedicated servers with backups and monitoring, and the design stage itself is a limited, agreed amount of engineering hours.