Start here: complete step-by-step guides

Python hosting on Cloud Ninza: the complete guide for Django, Flask and FastAPI

Every step for a Python app: account, plan, payment, code upload or Git, virtual environment, requirements, gunicorn start command, environment variables, database and migrations, static files, domain DNS, SSL, email records, backups and support.

  1. Create your Cloud Ninza account
  2. Choose the plan
  3. Your domain, or a free address
  4. Pay — and it is created automatically
  5. Put your code in and start it
  6. Database
  7. Point your domain to Cloud Ninza (any registrar or Cloudflare)
  8. Free SSL (HTTPS)
  9. Email: mailboxes, and SPF, DKIM and DMARC so every email arrives
  10. Deploy from GitHub, GitLab or Bitbucket (optional)
  11. Terminal, SSH and the File manager
  12. Backups and restore
  13. Upgrade your plan
  14. Renewals, invoices and payments
  15. Account security and sharing
  16. Support
  17. Go-live checklist
  18. If something is not working

Create your Cloud Ninza account

  • Go to cloudninza.com → Get started (or Log in → Create an account). Enter your name, email, mobile number with country code, country and a password of at least 10 characters.
  • We email you a 6-digit code. Type it on the next page to confirm your email. No code? Check spam, or press Send a new code. Mistyped the email? Change it on the same page.
  • You land on the Console home. To sign in later: cloudninza.com → Log in, with your password or Login using email OTP (a code to your email).
  • Recommended now: Account → Settings → Two-step verification — scan the QR code with Google Authenticator, Microsoft Authenticator or Authy, and keep the recovery codes somewhere safe.
  • Optional but useful: Account verification (PAN for individuals; PANIN or another registration number for a business).

Choose the plan

  • Press Create app (top bar) or Launch an app (sidebar). The location is India.
  • Pick the blueprint Python (Django, Flask, FastAPI) and its version (the recommended one is preselected).
  • Pick the plan: Starter for one small app, Growth for most businesses, Business and Pro for more apps, storage and app memory (RAM). Every plan has free SSL, backups twice a day and free email accounts. You can upgrade later and pay only the difference.
  • Pick the term: 1 year, or longer terms that cost less per year.

Your domain, or a free address

  • I have a domain — type it without www (for example yourbusiness.com). You buy domains at any registrar (GoDaddy, Hostinger, BigRock, Namecheap…); Cloud Ninza does not sell domains.
  • Give me a free address — type a name and it becomes name.cloudninza.in, live with HTTPS at once. The box shows available, taken or not allowed as you type. You can connect your own domain later from Domains — the same site moves, nothing to re-upload.
  • Have a coupon or a referral code? Enter it and press Check code — the total updates before you pay.
  • Tick the box agreeing to the Terms of Use and Acceptable Use Policy. The Create button works only after the tick.

Pay — and it is created automatically

  • Press Create. The payment window opens straight away: UPI (GPay, PhonePe, Paytm), cards or netbanking, through Razorpay.
  • Paid with a 100% coupon or wallet credit? There is nothing to pay — the order is confirmed at once.
  • You see Payment received with your Invoice PDF and Receipt PDF; both are also emailed.
  • Your site is created automatically, usually within minutes. An email tells you when it is ready. Find it under My apps and sites.

Put your code in and start it

  • Upload the project into the app folder with File manager, SFTP or Git deployments. Include requirements.txt; leave out venv, __pycache__ and .env.
  • App settings: choose the preset (Django, Flask, FastAPI/ASGI, WSGI) and the Python version (3.10 to 3.14). Each app has its own virtual environment; Deploy runs pip install -r requirements.txt.
  • The start command runs gunicorn on 127.0.0.1:$PORT (Django: yourproject.wsgi; FastAPI: with the Uvicorn worker). Put secrets in Environment variables, never in code.
  • Django: set ALLOWED_HOSTS to your domain, DEBUG=False, and run python manage.py migrate and collectstatic with Run a command (or cn-env in the Terminal). Static files are easiest with WhiteNoise.

Database

  • Databases → Create (PostgreSQL or MariaDB/MySQL) and use host localhost in DATABASE_URL or your settings.
  • SQLite works for small sites; the file lives in your app folder and is included in the backups.

Point your domain to Cloud Ninza (any registrar or Cloudflare)

  • Open Domains in the dashboard. It shows our server IP and checks your domain live: Points here, Through Cloudflare, or where it points now.
  • At the company that runs your domain's DNS add (or edit) two records: Type A, Name @, Value = our IP — and Type A, Name www, Value = the same IP. Delete any other A or AAAA records for @ and www.
  • GoDaddy: My Products → your domain → DNS → Add / Edit record. Hostinger: Domains → your domain → DNS / Nameservers. BigRock: Domain → Manage DNS. Namecheap: Domain List → Manage → Advanced DNS. Use TTL "1/2 hour" or the lowest offered.
  • Cloudflare: DNS → Records → edit the A records for @ and www. The orange cloud (Proxied) is fine for the website. Under SSL/TLS choose Full (strict) — never Flexible, which makes https loop.
  • Changed the nameservers instead (to Cloudflare or elsewhere)? Then the records must be added at that new DNS host — edits at the registrar no longer count.
  • Most visitors see the change within minutes; allow up to 24–48 hours for everyone. Domains turns green when it points here.
  • Changing A records never moves your email. Leave MX records alone unless you are moving email to us.

Free SSL (HTTPS)

  • Nothing to do: a free Let's Encrypt certificate is issued automatically for your domain and www as soon as they point here, then renewed automatically. Always use HTTPS is switched on with it.
  • On Domains you see which names are covered, which are still waiting and why. Check and issue now retries at once.
  • Free cloudninza.in addresses have HTTPS from the first minute.

Email: mailboxes, and SPF, DKIM and DMARC so every email arrives

  • Mailboxes (you@yourbusiness.com): Email → Set up email for the domain, then Create a mailbox. Your plan includes free mailboxes — the Email page shows how many.
  • The Email page lists every DNS record with a live Found / Missing check and Copy buttons. Add them where your DNS is (registrar or Cloudflare):
  • MX at @ → mail.yourbusiness.com, priority 10 — only if your mailboxes are with us. Using Google Workspace, Microsoft 365, Zoho or GoDaddy email? Do not change MX.
  • A mail and A webmail → our server IP. In Cloudflare these two must be DNS only (grey cloud) — Cloudflare cannot carry email.
  • SPF — ONE TXT record at @: v=spf1 a mx include:spf.clients.cloudninza.com ~all (with Google Workspace: v=spf1 include:_spf.google.com include:spf.clients.cloudninza.com ~all). Already have SPF? Edit it and add include:spf.clients.cloudninza.com — never two SPF records.
  • DKIM — TXT record named mail._domainkey, value copied from Domains → Email from this website (it is unique to your domain).
  • DMARC — TXT record named _dmarc: start with v=DMARC1; p=none; rua=mailto:you@yourbusiness.com, and move to p=quarantine after a few weeks.
  • Even without mailboxes here, add SPF and DKIM: your website's own emails (contact forms, orders, password resets) are only sent once they are found.
  • Read mail at Email → Open webmail (signs you in, no password), or set up phones and Outlook: incoming IMAP mail.cloudninza.com port 993 SSL, outgoing SMTP mail.cloudninza.com port 465 SSL or 587 STARTTLS, username = the full email address.
  • Run Email health check to send a real email in and out and see what to fix.

Deploy from GitHub, GitLab or Bitbucket (optional)

  • Git deployments → connect the repository and branch. For a private repository press Create deploy key and add the shown key to the repository (read-only).
  • Add the webhook URL shown there to the repository, and every git push deploys by itself: the code is fetched, built, put live in one step and health-checked.
  • A release that fails to start is rolled back automatically. Releases keeps earlier versions; Make live switches back in one click.

Terminal, SSH and the File manager

  • File manager: upload, edit, extract zips, change permissions, in the browser. Up to 100 MB per upload.
  • Terminal: a full shell in the browser, in your own isolated account.
  • SSH and SFTP access: add your public key (or generate one) and connect with any SSH or SFTP app (FileZilla, VS Code SFTP extension). Sign-in is by key only.
  • Cron jobs: run a command on a schedule. Logs: see the website's access and error logs.

Backups and restore

  • Every project is backed up automatically twice a day (12 AM and 12 PM), off-site, and every backup of the last 30 days is kept.
  • Backups → Restore from a daily backup: pick the project, a date and time on the calendar, then what to restore (the whole site, one folder or file, a database or a mailbox) and how: to a separate folder, as a download, or replacing the live copy (the current version is saved first).
  • You can also make your own backup any time under Backups. Deleted something? Check Trash first — deleted files, databases, mailboxes and projects stay there for 7 days.

Upgrade your plan

  • My apps and sites → Upgrade on the project's row. Choose a bigger plan: you pay only the difference for the days left until your renewal date.
  • The bigger storage, websites and memory apply within a minute of payment. Files, databases, email and settings stay exactly as they are; nothing restarts.
  • A smaller plan is possible when your sites and files fit it — there is no refund and no wallet credit for the rest of the term, and the next renewal is at the lower price. Every change asks you to confirm in a popup.

Renewals, invoices and payments

  • Nothing is ever charged automatically. Reminders are emailed from 30 days before the renewal date; Billing shows Upcoming payments and every invoice with its PDF.
  • Renew from My apps and sites → Actions → Renew (1 year or longer terms, coupon box, wallet credit).
  • Not renewed by the renewal date? The project is suspended the next day (offline, data kept and backed up). Pay within 30 days and everything comes back, with the term continuing from the original date. After 30 days the project is deleted.
  • All payments are final; there are no refunds. Refer someone with your link under Referrals and earn wallet credit on their first payment.

Account security and sharing

  • Password vault keeps your WordPress and email passwords encrypted; Show and Copy them any time, or change them there.
  • Two-step verification (authenticator app or email codes) under Settings. Activity log lists every action on your account.
  • Share access gives a developer or colleague access to ONE project with their own Cloud Ninza login — Development (tools only) or Full (also renew and change plan). You never share your password.

Support

  • Support tickets in the dashboard (choose the project — we see the right server at once), WhatsApp or call +91 74500 06987, or email hello@cloudninza.com. 24x7, answered by the engineers who run the platform.
  • The Help center has a step-by-step guide for every task; the search box finds them as you type.

Go-live checklist

  • The app opens on the free or temporary address and works.
  • Domains shows your domain and www pointing here and a certificate for both.
  • Open https://yourdomain and https://www.yourdomain — both load with the padlock.
  • Email: SPF and DKIM show Found; a test from your website (contact form, password reset) reaches a Gmail inbox. Mailboxes receive mail.
  • Make one manual backup under Backups before announcing the launch.

If something is not working

  • Site still shows the old host: DNS has not changed everywhere yet, or an old A / AAAA record remains — check Domains and the guide Website not opening after a DNS change.
  • Too many redirects behind Cloudflare: set SSL/TLS to Full (strict), never Flexible.
  • 502 or 503: the app is stopped or crashing — read Logs, then Restart. 500: the code's own error — see the error log.
  • Emails not arriving: SPF or DKIM missing — Domains → Email from this website shows which.
  • Storage full: delete old backups and files, or upgrade the plan.
  • Still stuck? Open a Support ticket for that project — an engineer answers, 24x7.

Stuck? Our engineers answer support tickets around the clock. Contact us, or create an account and open a ticket from the dashboard — the same guides are there too.

Next step

Move your site, or your whole cloud estate

Shared hosting you can buy in two minutes. Infrastructure and managed services quoted by an engineer within one business day.