Skip to content
BetaOnboarding developers in small groups

Push your code. We run the rest.

Laravel, Node.js, Python, PHP and WordPress, with databases, domains and SSL built in. Top up your wallet by card, and pay only for the hours your apps are awake.

  • No servers to manage
  • Every app in its own sandbox
  • Billed hourly, capped monthly

Every service in the project with its live status, this month's cost and the latest backups.

Project, in the Tanzahost dashboard
  • Sandboxed by default

    Every app runs locked in its own sandbox, with its own limits and its own private network. A neighbour's bad day never becomes yours.

  • Charged by the hour

    A prepaid wallet, charged every hour for the memory and processor time your apps used. No plans to choose, and sleeping apps pay for storage only.

  • Certificates on autopilot

    Issued the moment your domain points to us, and renewed before they expire, without you ever noticing.

  • Backups that stay put

    Encrypted 5 days a week and kept 7 days in another location. The servers can add backups, but never delete them.

From repository to live, in three steps.

  1. Bring your code

    Connect a GitHub repository or upload a ZIP. We recognise Laravel, Symfony, Next.js, Django, FastAPI, WordPress and more, and build it for you.

  2. Add what it needs

    A MySQL, PostgreSQL or Valkey database in one click. Its connection details go into your app's variables, under the names your framework expects.

  3. Go live

    Your app gets a free address with SSL straight away. Point your own domain at it, and its certificate follows within a minute.

Every version, side by side.

Your PHP 8.0 shop and your neighbour's PHP 8.5 app run on the same platform without ever touching. We read your code, detect the framework, and build it the way it expects.

Something special to install? Add a small settings file to your code with the versions, packages and commands you need.

A month has 730 hours. Pay only for the ones you use.

Every hour, your wallet pays for the memory and processor time your apps really used. There are no plans: set each app's limits, and apps that sleep pay for storage only.

Top up by card: Visa, Mastercard or American Express, or with Apple Pay and Google Pay. Payments are handled by Stripe.

Estimate your month

Reading the prices

Your dashboard never needs a refresh.

Deploys, requests, payments and alerts arrive the moment they happen, on your laptop and your phone at once.

  1. Live build and request logs

    Follow every line as your app builds, starts and serves visitors.

  2. Rollback in one click

    The live build and the one before it are kept. Go back with one click, without downtime.

  3. A terminal in your browser

    Run artisan, composer or npm inside your app, safely.

  4. A bill you can watch

    See this hour's cost as it happens, not as a surprise at the end of the month.

Activity

Live
  • Deployment #48 of web is liveduka · Add card checkout · built in 30 s2 minutes ago
  • Wallet topped up by card$20.00 · receipt sent1 hour ago
  • Attack stopped at the front doorSQL injection · duka.co.tz/search2 hours ago
  • duka-api is sleepingWakes on the next visit, in about a second3 hours ago
  • Backup of duka finished312 MB · encrypted · stored in another location12 hours ago
  • SSL certificate renewedduka.co.tz and www.duka.co.tzyesterday
Streaming

GET/products?page=220061 ms

POST/cart/add20174 ms

GET/checkout20092 ms

POST/wp-login.php403blocked

POST/api/payments/callback20041 ms

JOBSendOrderReceiptdone210 ms

GET/orders/104220057 ms

GET/images/chai-ya-tanga.webp20012 ms

1,284 requests in the last hour · 0 errors · typical response 64 ms

Walls within walls.

On a shared platform, assume every app will be attacked one day. So an attacker has to get through four walls to reach your data, and the first one stops almost everything.

  • One sandbox per app

    Hard limits on memory, processor and processes, and a private network of its own.

  • No open doors

    The servers your apps run on have no public ports at all. Visitors only ever reach the front door.

  • A guarded front door

    A web firewall, bot blocking and rate limits stop attacks before your code sees them.

  • Everything on the record

    Every action in your account is logged, and backups are encrypted and locked against deletion.

Four walls around every app: the network's edge filters floods, the front door's web firewall stops attacks, the private network has no public ports, and each app's sandbox has hard limits.

Your domain, live in a minute.

We check your DNS live and issue SSL the moment it's ready. Connect it whichever way suits you.

  1. Use our nameservers

    We copy your existing records first, so your email keeps working, then look after every record for you.

  2. Connect Cloudflare

    If your DNS is at Cloudflare, approve access on Cloudflare's own page, for DNS only. We manage the records there.

  3. Add records yourself

    Keep your DNS where it is. We show the two records to add, then check for them every minute.

DNS records for duka.co.tz

ns5.tanzahost.com · ns6.tanzahost.com

Uses Tanzahost's nameservers
  • A@

    Managed

    203.0.113.10

  • AAAA@

    Managed

    2001:db8::10

  • CNAMEwww

    Managed

    duka.co.tz

  • TXT_domain-verify

    Managed

    domain-verify=51c0d9a7e2f4

  • MX@

    Yours

    1 smtp.google.com

  • TXT@

    Yours

    v=spf1 include:_spf.google.com ~all

  • TXT@

    Yours

    google-site-verification=Xq4rT0Zc

  1. Waiting for DNS
  2. Points to us
  3. SSL issued
  4. Live

Hosting, rebuilt from the ground up.

Classic hosting compared with Tanzahost
How you payClassic hostingA fixed yearly plan, used or notTanzahostBy the hour, from a prepaid wallet, for what your apps use
Getting code onlineClassic hostingFTP and a file managerTanzahostGitHub or a ZIP, deployed without downtime
Apps on one serverClassic hostingShare one web server and its settingsTanzahostEach locked in its own sandbox
Node.js and PythonClassic hostingLimited, if offered at allTanzahostFirst-class, next to PHP
Seeing what happensClassic hostingLogs you download laterTanzahostLive logs, costs and alerts
Getting helpClassic hostingOpen a ticket and waitTanzahostSali checks your apps and explains, any time, then a person
LeavingClassic hostingAsk for a backup, and hope it's completeTanzahostExport your code, databases, DNS and backups whenever you like

Pick where your project lives.

Every service in a project runs in the same location, side by side, so your app and its database talk in under a millisecond.

We open new locations wherever we add servers.

Where your data lives

Apps and databases
In your project's location
Backups
Encrypted, in a second location
Questions to Sali
An outside AI service, never with your secrets
Card details
Typed only on Stripe's secure page

Sali checks before it answers.

Ask why your site is slow or broken. Sali, our AI assistant, reads your logs and numbers, explains the cause in plain words, and changes nothing until you click.

SaliAI assistant

Why is duka.co.tz showing an error?

Your latest deployment expects an orders table that doesn't exist yet: the migration create_orders_table hasn't run on your live database.

SQLSTATE[42S02]: Base table or view not found: 1146

Table 'duka.orders' doesn't exist

Nothing changes until you click.

Sali is an AI assistant, and can be wrong. Its answers come from an outside AI service, under our privacy policy. Your passwords and secrets are never sent to it.

We'll move your cPanel sites for you.

Your hosting keeps running as it is. When moving opens, we bring over your sites, databases, mailboxes and DNS, with a moving plan made for your account.

Contact us

Straight answers.

Something else on your mind? Email us.

Do I need to know how servers work?
No. You bring your code; we build it, run it, secure it and keep it online. There's nothing to install, and no server to look after.
How does paying by the hour work?
You top up a prepaid wallet. We measure the memory and processor time your apps use every minute, and charge it every hour. There are no plans: each app has limits you set, so a runaway app can't empty your wallet, and an app that sleeps pays for its storage only.
What happens if my balance runs out?
We remind you when 7, 3 and 1 days are left, and again at zero. After a short grace period your apps stop, but nothing is deleted: your DNS keeps answering, your data is kept for 30 days, and everything starts again within a minute of a top-up.
Can I use my own domain?
Yes. Every app gets a free address on tanzahost.co, with SSL, straight away. Connect your own domain with our nameservers, through Cloudflare, or with two records where it's registered, and its certificate follows within a minute.
Is my app safe from other customers?
Each app runs in its own sandbox, with hard limits and a private network of its own, and the servers have no public ports. Visitors only reach our front door, where a web firewall checks every request.
Can I take everything and leave?
Yes, whenever you like. Your code, your databases, your DNS records and your backups can all be exported from the dashboard. No lock-in.
Where does my data live?
In your project's location, such as UK-01 in the United Kingdom, with its backups in a second location. If you ask Sali for help, your question is answered by an outside AI service, under our privacy policy; your passwords and secrets are never sent to it.
Can I host email?
Yes. Turn on email for your project's domain, and make mailboxes like info@ and sales@, with aliases, forwarding and auto-replies. Read your mail in our webmail, or on your phone and in Outlook. Each mailbox is a small price a month, plus its storage.

Build something. We'll keep it running.

Create your account in a minute, add a little to your wallet or save a card, and deploy your first app with a free address and SSL.

What happens next

  1. 1

    Create your account

    With your email, Google, GitHub or a passkey.

  2. 2

    Top up, or save a card

    By card, or with Apple Pay and Google Pay. With a saved card, you pay once a month for what you used.

  3. 3

    Deploy your first app

    From GitHub or a ZIP, with a free address and SSL.