Hosting

We put it on
a cheap cloud.
You skip the rack.

We deploy your solution on any cloud space, yours or one we pick, keep the instance running, and shut the GPU down when the batch is done. Cheaper than buying hardware when the data can travel.

Some projects can skip a Nairobi GPU you own. If the data can travel, cloud AI is the cheaper path: we stand the model up on any cloud space, wire the API, and you pay for the box, the box itself, with token meters and capital purchases left out.

Any
Cloud host
On/off
Batch GPUs
Us
Deploy + watch
Move
To on-prem later

What you buy

A running system in hand, free of a console-login handoff.

We deploy it

Your model or a Corvux-built app, containerised, HTTPS in front, storage attached. You get a URL and credentials, free of a homework list.

We pick a cheap box

Any cloud space that fits. You name the host, or we choose the cheapest SKU that week for CPU or GPU.

We stop idle GPUs

Batch windows start the instance and kill it after the queue. Same idea as a scheduled inference job, 3 a.m. idle time stays off the bill.

We can move it home

If counsel later says the data must stay in Kenya, the same stack goes onto your hardware. Cloud is a start you can leave.

$ corvux cloud status --host any --job imaging-pilot
REGION public cloud (outside Kenya, approved for this pilot)
SKU L4 · scheduled 3h window
STATE stopped · last run 41 min · $0 idle
BILL compute + disk this month < big-cloud list
✓ promote path: same image → Nairobi colo

When to skip this

Cheap is wrong if the law says stay.

Most public clouds never have a Kenya GPU region. Patient images and bank customer files are a Section 48 transfer question, and sometimes a Section 50 Kenya-server question. They belong elsewhere. We will say that on the first call and quote on-premise or Nairobi colo instead. Cloud AI is for workloads you and your counsel are willing to host off-shore, demos, non-sensitive ops, and pilots that need a price this month.

01
Scope the job
Model, traffic, and whether any personal data leaves Kenya. That answer picks the host.
02
Stand up the cloud box
Any host. GPU or CPU, disk, backups, TLS, and a deploy pipeline you can see.
03
Schedule and watch
Start/stop for batches, uptime for APIs, a monthly bill you can read in one screen.
04
Keep or relocate
Stay on cheap cloud, or lift the same containers onto Kenya hardware.

Pairs with business solutions, custom scripts that need an always-on box, and on-prem vs cloud if you are still deciding. If the thing on the box is a model file, see model hosting.

FAQ

Cost questions, answered without theatre.

Which cloud do you use?

Any cloud space that fits the job and the budget. You name the host, or we pick a cheap one. Vendor lock-in stays off the table.

Does the data stay in Kenya?

A typical public cloud keeps it elsewhere. If the data is sensitive under the KDPA, we recommend on-premise or Nairobi colo instead, same software, different box.

What do you deploy?

Your model or ours, an API, storage, HTTPS, backups, and a start/stop schedule so idle GPUs stay off the overnight bill overnight.

Can we move later?

Yes. We containerise so the same stack can move from one cloud to another, or onto your own hardware, if compliance or volume changes.

Need it hosted, hosting, ahead of a hardware quote?

Tell us the model or the app and the monthly budget. We will say which cloud, or on-prem, with a number.

Request cloud deploy