Agency Brief
Taking on a client's Python app without taking on their infrastructure
Somebody built a Django site for your client and left. Now it is yours, and the first honest question is whether it belongs on an account you can administer at all.
Straight answer first
Business hosting runs an ordinary Flask or Django site cleanly with Postgres beside it, and VPS territory starts the moment Celery, channels or system packages appear — inherit the first sort happily and quote properly for the second.
Most studios meet Python because a developer left and a client needs somebody. Before you agree to anything, establish which interpreter it runs on, whether it needs background workers, and whether the previous owner installed anything at system level. Those three answers decide whether this is a modest line on your platform bill or a managed server you have just adopted for free.
Written by the Hosting Seller staff · Checked 4 August 2026
NVMe
Storage under every client account
Free
Domain, year one on annual orders
99.9%
Uptime target we hold to
Flat
Price at renewal, per account
Written for studios and resellers who did not choose Python but now support it. The framework documentation assumes you control the server; the commercial reality is that you control a panel and a client's expectations, which is a different problem and a far more common one.
Read the Django deployment notes and they quietly assume WSGI serving, isolated environments and a real database. Those three assumptions double as a triage tool: an app that fits them can live on a shared-class account for very little a month, and an app that does not is a server, whatever the previous developer preferred to call it.
Triage before you agree to anything
Four questions, asked in this order, tell you what you are taking on. Which Python version does it run? Is there a requirements file, and does it still install? Does anything run outside the request cycle — Celery, channels, a scheduled scrape? And is there a system package somebody installed by hand that the app quietly depends on?
Two yeses to the last pair and you are looking at a VPS. Otherwise a WSGI app with a virtualenv, Postgres and static files served properly is comfortable on Business hosting, and you can say so with confidence rather than optimism.
The version conversation, held before the quote
Interpreters move on and client apps do not. Establish which version the code needs while you are still quoting, because 'it runs on my machine' is not a hosting specification and discovering the gap after you have taken the account is a conversation you will be paying for.
Say plainly what an upgrade would involve, and price it separately from the hosting. Clients accept the cost of modernising far more readily when it arrives as its own line than when it surfaces as a mysterious increase in a monthly fee they believed covered everything.
Cron, workers, and the invoice they justify
Cron plus a virtualenv covers the classic automation workload — scrapers, reports, nightly syncs — with no server to look after, which is genuinely the cheapest dependable scheduler you will ever operate on a client's behalf. Stay within the process limits and it will run for years without attention.
What it does not cover is a queue with a supervisor and a monitoring dashboard. When you cross that line, cross it visibly: a separate service with its own price, rather than a favour that quietly hardens into an expectation.
Handing it over without handing over your panel
Sooner or later a client brings development in-house and wants access. Give them a cPanel account of their own inside your WHM rather than the credentials to a shared account, and the handover becomes a login and a scope rather than a fortnight of untangling.
Keep the backup habit while you do it. A backup runs daily on every plan and restores from the panel in minutes, so the moment before a handover is a good moment to prove the copy actually restores — which is also the moment you discover whether anybody ever tested it.
We sell the hosting. That is the whole disclosure.
There is no referral fee behind the recommendation on this page. We are the supplier, we would like the account, and the rest of the page is more useful to you once that is out of the way.
What you pay on day one is what you pay at renewal, which is what lets you quote a client a standing charge and still be comfortable with it in year three.
- Tests you can run before you commit a client
- One trade price, held at renewal
- Free migration for the sites you already host
- A refund policy with no small print
Why Hosting Seller
On every plan, as standard
Postgres without a server
PostgreSQL sits alongside MySQL on Business plans, so a Django client does not automatically become a machine you have to patch.
Virtualenvs and pip, unrestricted
Shell access on developer plans means environments are yours to build rather than a support request with a queue in front of it.
Matched to this verdict
The Business Standard plan is this page's recommendation made concrete — one flat price, essentials included, upgradeable in place.
A ladder for the awkward client
Shared, VPS and dedicated under one supplier, so the app that outgrows its account moves up rather than moving out.
Restores you can run yourself
A daily backup on every plan and a restore from the panel in minutes, which is the difference between an incident and a catastrophe.
A supplier with a company number
IGI Security Services Ltd, registered in England and Wales — a public record you can check before you put a client's business on it.
Price Tags Compared
How we compare with the household names
Typical sign-up and renewal prices across the market, set next to ours — the second number most comparison charts leave off.
| Line item | Hosting SellerBest seller | Typical big-brand host | Typical budget host | Typical loss-leader |
|---|---|---|---|---|
| Entry price / mo* | $2.42/mo | $4–$6 | $2–$4 | $1–$3 |
| Price at renewal / mo | $2.42/mo | $10–$15 | $8–$12 | $4–$6 |
| Renewal price on the entry plan is unchanged | ||||
| SSL on every plan | ||||
| Site migration included | ||||
| The entry plan uses NVMe storage | ||||
| Entry plan gets a backup daily | ||||
| Live human support, 24/7 |
*The number in our column is the cheapest plan on our shelf, priced on an annual term and pulled live from the very catalogue that feeds the pricing page, so it cannot drift out of date. Other columns show the ranges shared hosting tends to advertise inside each bracket: introductory rates that normally ask for a one-to-four-year commitment, then climb once that term expires. Naming individual competitors and printing their prices is something we have stopped doing. A figure we cannot re-check on the day you read it has no business sitting in front of you. So compare us with whoever you are genuinely weighing up, and read the renewal line first. That line tells you more than the headline ever will.
First Steps
From choosing to live
- 1
Triage before you take it on
Interpreter version, requirements file, background work, system packages. Four answers, ten minutes, and you know whether this is a hosting line or a server.
- 2
Quote the upgrade separately
If the app needs a newer runtime or a rewritten deployment, that is a project with its own price. Folding it into a monthly fee is how studios end up working for nothing.
- 3
Prove the restore before the handover
Take a backup, restore it onto a staging copy, and check it truly comes back. Do it while you still have the money-back window and the client's goodwill.
In the Box
Packed with every plan
- SSH, Git and Composer on the plans built for developers
- PostgreSQL alongside MySQL on Business plans
- Real cron for scheduled scripts and scrapers
- A backup taken daily, with restores you run yourself
- Staging copies so a change is proved before a client sees it
- PHP versions picked per site from the panel for mixed client books
- Free SSL on every site, reissued before it lapses
- Site migration done for you by our staff, at no charge
- One-click installs for WordPress and 240+ other applications
- Upgrades applied to the account in place, with no move between plans
Across the Counter
Things people ask us all the time
A client's developer has vanished. What do I check first?
Whether the code is in version control and whether the requirements file still installs. If both are true you can rebuild the environment anywhere and you have a real negotiating position. If neither is, your first billable job is not hosting — it is getting the project into a state where hosting is even a question.
Can I keep several client Python projects on one account?
Quiet ones, yes — separate virtualenvs and separate databases keep them apart tidily, and the addon domain allowance is generous. Anything with real traffic or a compliance-minded client deserves its own account, both for the headroom and because suspending one should never affect another.
How do I give a client's in-house team access without losing control?
Create them their own cPanel account under your WHM rather than sharing a login. You keep the master panel, the limits and the ability to suspend; they get exactly the site that is theirs. It also turns a handover into an afternoon rather than an audit.
Is it my problem when their scraper gets blocked?
Only if your contract says so, and it should say. The platform, the network and the panel are ours; the application's behaviour against third-party sites is the client's. Write that boundary down before the first incident, because afterwards the conversation is a great deal harder.
Read next
Hosting With Free SSL
Certificates on every client site without a per-account fee — what that is worth across a book of forty.
Hosting With DDoS Protection
Keeping a client's site up when it draws the wrong sort of attention, and who explains it to them afterwards.
Business Hosting
Shared hosting with the developer kit: SSH, Node.js, Python and PostgreSQL.
SSL Certificates
SSL free on every plan, with wildcard and EV on the shelf if needed.
Moving your site to another host? Start with this checklist.
A step-by-step order of work for a move your visitors never spot: which files to copy first, how to carry email across without losing one message, the right moment to repoint DNS, and the two mistakes behind nearly every hour of downtime people ring us about.
Adopt the app on your own terms.
Postgres beside MySQL, real cron, shell access and free migrations — with a per-client cost you can actually quote.
See Business Hosting plans