What's new.

Sali used to explain what was wrong and offer a button. Now it can do the fix for you, as you, once you say yes.

What's new

• A card before anything happens: Sali shows exactly what it will do. Choose Allow once, Always allow in the project for small, safe things, or Not now.

• Fixes in a few steps: add a missing PHP extension and deploy again, add or change DNS records, set variables (you type the values; Sali never sees them), add a domain, connect a database, change limits or add a worker.

• Money and risky steps are asked every time, with the price from our price list on the button, or the app's name typed to confirm.

• Undo for 24 hours, on the card and in your activity.

• Your permissions, never more: Sali can do only what you could do yourself, and never deletes anything or touches payments.

Example

Asha's Laravel build fails with "ext-intl is missing". She asks Sali why. Sali replies with a card: Add the PHP extension intl to duka-web and deploy again. She taps Allow once, the new version goes live, and her activity says Asha (with Sali) added intl to duka-web. If she changes her mind, Undo puts the settings back and the version before.

Sali's answers about how Tanzahost works now come from our own pages, the same ones you can read, and each answer says which page.

What's new

• Every page: the docs, the guides, the help center, the technology pages, the comparisons, the moving guides, the changelog, the blog, the pricing page and the legal pages, in the dashboard's chat and on the website's.

• Today's prices: a page that names a price shows Sali today's, like $5.99 per GB of memory a month.

• A link to the page: each answer links the page it came from, so you can read the whole of it.

• No guessing: when our pages don't say, Sali tells you so, and our team sees the question, so the missing page gets written.

• News on the blog: posts about new features, written with Sali and checked by our team before they're published, and marked so.

Example

Asha asks Sali How much is 1 GB of memory a month? Sali answers with today's rate and links the pricing page. She asks Can I host Rails?, and the answer links Ruby on Rails hosting.

The app catalogue grows from the admin panel now, and every app in it is checked and tried on a real server before you see it.

What's new

• Search the catalogue by name or by what you need ("blog", "shop", "chat"), narrow it by category, and see featured and new apps first.

• More apps as each one passes its checks: Ghost for a blog and newsletter, Nextcloud for files and calendars, Mattermost for team chat, Umami for website visits, plain WordPress and a Laravel starter, beside WordPress's shop, school and events versions, Odoo, Metabase, Uptime Kuma and Gitea.

• Before you install: each card shows about what the app costs a month, what it makes for you (like "+ MySQL database") and its licence. The install page asks the app's own questions and lets you change its limits.

• Kept up to date: new versions are found by themselves, checked for known security holes and tried before they're offered. If a version you run is later found to have a hole, you get one email and a bell message, with Update on the app's card.

• Can't find an app? Choose Suggest an app and it reaches our team.

Backups now bring back exactly what you lost, nothing more.

What's new

• Browse files: next to any backup, open your apps' kept folders a folder at a time, or search by name.

• Restore this file or folder: it goes back where it was. The file you have now is kept beside it (logo.png.before-restore-2026-10-27) unless you tick Replace it. Download this file gives you just that one, up to 2 GB.

• A DNS zone from a backup: see the difference first, then put back only the records. It's one change in the zone's history, so you can undo it.

• What a backup holds, on the Backups tab: files, databases, mailboxes, DNS zones and your apps' settings (variables' names, never their values).

• Backing up… waiting for its turn: a backup that has to wait says just that, then Done.

• Your own Google Drive, recommended: the card sits at the top of the Backups tab until you set a plan.

• If a server stops for good, your project comes back on a new one from its newest backup, your own databases to within 5 minutes. You're told before and after.

• Our team can restore for you when you ask; you get an email saying who did it and why.

Example

Asha deletes her shop's logo.png by mistake. On her phone: Backups → Browse files on yesterday's backup, wp-content/uploads/2026/10, logo.png, Restore this file. It's back in 20 seconds.

You always know where you are, and an app gets the database it needs without you opening another page.

What's new

• Account / project / service in the top bar: on an app's page it reads Asha's account / Shop / shop, with a menu at each step. One click on Shop goes up to the project.

• A project opens on what it holds: one app or site opens straight on it, and so does a project with just a database. Two or more apps open on a map of the project's services.

• The services map: apps and sites on the left, databases, caches and storage on the right, with a line from each app to what it uses. On a phone, each app says what it uses. A database says who uses it: "Shared with web and api".

• Projects has its own page: every project in the account at Projects, and New project beside it.

• Databases that make themselves: add a Laravel app from GitHub and, before you deploy, the page says "This is Laravel and uses MySQL", with the price a month first. Keep the switch on, and the database is made and connected before your first version starts, its migrations run on deploy, and PHP gets its database extension. Laravel's default sqlite becomes MySQL, so your data isn't lost at the next deploy. Prisma, Drizzle, Django, Rails, WordPress code and Node.js and Python drivers are read too, and a Valkey cache is offered when your code uses Redis.

• Make one and connect it: an app that expects a database it hasn't got gets the same button on its page, beside Connect an existing one.

Read Projects and locations and Connect an app to a database.

A cPanel account moves here from any host with one file, and we never touch your old host.

What's new

• Move from cPanel on your dashboard: upload your full backup (it carries on if your connection drops) or paste a Google Drive or Dropbox link to it. Up to 20 GB; our team brings bigger ones.

• The plan first: your sites with their apps and PHP versions, databases, mailboxes, DNS records, cron jobs and what can't move, read from the file, with the monthly cost. Leave out anything you don't want. Nothing is made until you choose Move it, free.

• Like nothing changed: each site checked for malware before it answers on its free address, settings files pointed at the new database (WordPress, Laravel, Joomla, Drupal, PrestaShop, OpenCart, WHMCS), WordPress viewable before you switch, mailboxes with the passwords people already use and every message, forwarders, filters and auto-replies, FTP logins as SFTP logins, cron jobs paused so nothing runs twice.

• Email before the switch: add one TXT record at your old host and your mailboxes are ready here.

• The switch, one domain at a time: bring a fresh backup on the day so the newest orders are here, change your nameservers, and we tell you when it's seen. One more backup a day later brings late email; we remind you.

• Undo the move, Start again within 7 days, and New passwords for every mailbox if your old host was ever broken into.

• Our team can prepare a move from a file you send to support; you check the plan and click Move it.

Example

Asha moves ashashop.com and ashabakery.com from another host. She downloads her full backup in cPanel, uploads it, and two minutes later checks the plan: 2 projects, 4 mailboxes with their passwords kept, 1 cron job paused. An hour later her shop opens on its free address. On Friday she brings a fresh backup and changes her nameservers; by the evening Juma's phone gets his mail here with the same password.

An app's variables, logs, versions and domains used to be project tabs with an app menu. Now everything about an app is on the app.

What's new

• Each service has its own tabs: an app has Overview, Versions, Variables, Logs, Numbers, Domains, Files and Settings. A site has Overview, Files, Database, Domains, Backups, Logs, Numbers and Settings. A database has Overview, Data, Users, Import & export, Backups, Numbers and Settings; a cache, Overview, Numbers and Settings; storage, Overview, Files, Keys and Settings. Links to a tab, and old links, land on it.

• The project keeps what spans its services: Overview, Backups, a new Activity tab, Settings, plus Domains once it has one, and Deployments and Logs once it has two apps or more.

• Maintenance mode for every app and site: visitors see "Back soon" with one line from you, while the app keeps running; you still open it with a password.

• Run a command: any one-line command, like php artisan cache:clear, run once in a copy of your app with its variables, its log live, the last 20 kept.

• The app's own activity on its Overview, and all of it a page at a time.

• Connected: what the app uses, with a database's connection details in a side panel, and each app's private name, like api.internal, which the project's other apps reach without leaving its network.

• Deploy on push and its branch change any time in Settings.

• Move one app to another project in the same location, with its databases if you choose.

• Its backups on its Overview, and its numbers over the last 30 minutes up to the last 24 hours.

• Settings in sections: Build and run, Scaling, Access, Email, Maintenance and the danger zone, one column, each setting once.

• A storage bucket's files in the browser: browse, download, upload and delete.

Read Your app's page, Maintenance mode, Run a command and Private names.

Your app's code is yours to change in the browser, whether it came from a ZIP or from GitHub.

What's new

• Every app's code opens in Files: one folder tree, with kept folders like Laravel's storage inside it, marked kept. Edit, upload a file or a ZIP, add, rename, move or delete, as on a site.

• Each change goes live by itself: saving says "Saved. Going live in about a minute…" and follows the version until it's live. Several quick saves go live together, and every save stays in the app's versions, so Go back to version 12 still works.

• Small changes in seconds: a PHP view, a template, a picture or a static page is laid on the version before, live in about 15 to 30 seconds. The deploy page says Quick change with the number of files. A change to composer.json or package.json makes a full version.

• Even when the last version failed: fix the file in Files and save, and it tries again.

• Apps from GitHub too: saving changes your app at once and opens a pull request in your repository, so your next push keeps the change. A push that would replace an unmerged change says so on its deploy page.

• Owners and developers can change files; viewers look only. A ready-made app's code stays as its makers publish it.

• Fewer words about builds: the dashboard says Versions, Version 12, Save and go live, Go back to version 12, Send version 12 to production and Try again.

• One way to add your code: the project's Add a service card has App or website. A classic PHP ZIP without Composer runs as a website by itself, anything else as an app, and you can switch before you deploy.

Read The file manager and Deploying.

Connect a repository or paste its link, and your app builds and goes live without you setting anything.

What's new

• The plan, before anything is built: the Add page reads your code and shows what it'll do, each line with its reason. For the open-source Laravel blog laravel-blog it says "Laravel 11 on PHP 8.4 (your packages accept 8.3 and 8.4)", the extensions added for its packages, Node.js 22 and Yarn 4.5.1 for its assets, a MySQL database, a cache for its queue and email from your project with their prices a month first, Horizon as a worker, and "Needs your key: Pusher (live comments)". Change any line before you deploy.

• Versions your packages accept: we read your lock file too, not only composer.json, package.json or pyproject.toml, and use our default when everything accepts it. No more builds on a version one of your packages refuses.

• Extensions and system libraries added for you: the ones your packages need, even when only the lock file names them, and the ones well-known packages use without saying, like gd for picture libraries. The most common ones are ready on every server, so most builds start straight away.

• Variables made and filled: APP_KEY, SECRET_KEY and the like are made for you and kept encrypted; your app's address, production settings and safe values from your example file are filled in; keys only you have are listed, never invented. A variable you set is never replaced.

• SQLite moves to a real database (MySQL, or PostgreSQL for Django and Rails), because a file database would be lost at every deploy. Choose Keep SQLite (one copy only) if you'd rather keep the file.

• Run the way your framework expects: PHP apps run on the same web server as our sites, several requests at a time, with .htaccess; migrations and the framework's other release steps run before each version goes live, and the build makes the public storage link; workers and the scheduler are set up from your code, with their prices shown first.

• Sample data when you ask: an app with a seeder offers Add the sample data once, and warns you first when it creates a login everyone can read in the code.

• Builds that fix themselves: when a build fails, we read why, fix what we safely can and try again, at most twice. If it still fails, the build's page says what went wrong, what we did and what you can do, with Fix it and Ask Sali.

• Ask us to add it: if your code needs an extension, a version or a service we don't offer yet, you're told in one sentence before anything is built, with a button to ask for it.

Read Deploy a Laravel app and Deploying.

Reselling is open to everyone, not only the people we invite.

What's new

• Apply from your account: Resell in the menu, with your business's name, website and a few questions. A person on our team decides, usually within a working day, and tells you why if it's a no.

• A setup checklist for new resellers: brand, panel address, records, your clients' login, and how your clients pay you.

• Your clients' login is made for you as soon as your panel's address answers. Nothing to ask us for.

• Your clients see their bills from you, on their Wallet page, in your brand.

Example

Juma's agency applies on Monday and is approved on Tuesday. By the afternoon his first client logs in at cloud.jumadigital.com.

We count what your apps use, minute by minute. Your card pays when your use reaches your line, $5 at first and growing ($10 and $50) as you pay, and at the end of every month for whatever's left.

Save a card to start: your first app, site or database starts once it's saved, and saving it charges nothing.

What's new

• Nothing left unpaid at the end of a month: on the 1st, your card pays whatever the month used, even if it never reached your line.

• No switch to remember: a saved card always pays. Remove it, and your wallet is prepaid until you save another.

• Topping up is still there, if you like to keep a budget: what's in your wallet is used before your card pays.

• Receipts that say what they paid: a card payment's receipt names the month whose use it paid for.

Read How billing works.

Your projects, in your pocket.

What's new

• Add to home screen from the Phone app card on your profile. On iPhone and iPad, tap Share, then Add to Home Screen.

• Notifications for the alerts you choose: turn them on for each device, and pick which alerts go to the phone app in your profile's alerts table.

• Quick actions: a crash or memory alert can open Restart or Roll back, and a low balance Top up. Each opens the page with its confirmation, so nothing runs from your lock screen.

• Send a test to check a device, and remove the ones you no longer use.

• Offline, the app says so, and opens again when you're back online.

Read Metrics and alerts.

A quick fix no longer needs your laptop.

What's new

• Code on an app's page opens its newest version: a file tree, up to 12 files in tabs, search by name or inside files, and colours for PHP, JavaScript, Python and more. Older versions open to read.

• A terminal under the code, when you ask for it.

• Save makes a new version with a short message, like "Fix the checkout total". Nothing goes live until you choose Deploy. If a newer version came in since you opened a file, we name it before saving.

• Apps from GitHub: each save also opens a pull request on your repository once you allow it. Until then, the version is saved here and the editor says the change isn't in GitHub yet.

• Preview any version at its own address before it goes live: for 1 hour, 4 hours or a day, with empty databases or a copy of staging's, locked with a password unless you open it. It stops by itself, and its price shows before it starts.

Read Environments and previews.

One currency, wherever you are.

What's new

• Every wallet is in US dollars, in every country.

• No currency to choose when you sign up.

• Dollars everywhere you look: prices on the website, estimates in the dashboard, card payments, top-ups and receipts.

• Tax works as before: where tax applies, it's inside the price and shown on your receipt.

Read Your wallet, card and top-ups.

We count what your apps use, minute by minute. Your saved card pays for it after you've used it, like a phone bill.

What's new

• Your card on the Wallet page: choose Save a card, and type it on the secure card page. We only see its kind and last four digits.

• At your line: when what you owe reaches your line, your card pays it that day. The line starts small and grows with each payment that goes through, and the wallet shows when your card pays next.

• On the 1st of each month, the card pays for whatever the month before left.

• A receipt for every payment, saying which month's use it paid.

• If the card is refused, or your bank asks to approve a charge, it's paused, your wallet is prepaid for now, and you get an email.

• Your spending cap still holds, so you decide what a month may cost.

Since 26 October, this is how every account pays: see Every account pays by a saved card.

Read Your wallet, card and top-ups.