Cloud Hosting help

Free is for testing: one app on a Technovize subdomain that sleeps on inactivity. Starter is fully managed production hosting — custom domain, auto-SSL, managed PostgreSQL, daily backups and business-hours email support. Business adds higher resource limits, 24/7 monitoring, tested restores with staging, zero-downtime deploys and priority same-day response.

To save resources, Free-tier apps spin down after a period of traffic inactivity. The next request wakes the process automatically, with a cold-start delay of a few seconds on that first load.

Yes — change plan at any time from your dashboard. Your app keeps running; you get more capacity, a custom domain and the extras of the higher plan.

Everything is charged in euros. As a Netherlands-registered company we apply Dutch VAT to domestic buyers, use EU B2B reverse-charge for valid EU VAT IDs, and exempt customers outside the EU from EU VAT. Every invoice is available as a PDF.

Your code, your bug fixes and your Python packages stay with you. We keep the platform underneath patched — operating system, web server, database and certificates.

No. You never log into a server: you push your code and we build and release it. That is what keeps the platform stable and secure for everyone on it.

A Django project holds proprietary business logic, architecture details and dependencies. A private repository keeps third parties from inspecting your code or spotting attack vectors.

We use a read-only SSH deploy key (or a scoped Personal Access Token) generated for your repository only. The server can fetch commits but can never write to or alter your source.

Secrets never live in Git. They sit in an encrypted .env on the host (or as secure environment variables in Docker), excluded from version control via .gitignore.

No. Deploy authentication uses a single-repository key limited to git pull. The server has zero access to your other repositories or account details.

Change the exposed keys straight away, set the new values in your app settings, and remove the secret from your Git history with a tool such as git filter-repo. Tell us as well — we can help contain it.

Automatically. When your app is created we set up the environment, the database, the web address and the certificate. You only add your public key and push your code.

Initialise Git locally, commit, create a private repo on GitHub, and push your main branch:

git init
git add .
git commit -m "Initial commit"
git branch -M main
git remote add origin git@github.com:your-username/your-repo.git
git push -u origin main

Change and test on your own computer, then run git push. We build the new version, release it and switch traffic over. That is the whole routine — the same command every time.

You do not deploy by hand. From your project folder:

cd my-project
git add .
git commit -m "wat ik veranderd heb"
git push technovize main

The release stops and your current version keeps serving. Nothing is switched over to a version that did not come up cleanly, so your visitors see the working site while you fix the migration.

Always test migrations locally against a PostgreSQL version matching production. Business plans get an isolated staging environment with an anonymised copy of production data to verify migrations first.

We handle PostgreSQL service health, memory, storage scaling and maintenance. Schema design, query optimisation and indexing remain the developer's responsibility.

Committing is not the same as sending. A commit only saves the change on your own computer; git push is what sends it to us. Check that your push finished without an error — the build takes a minute or two after that.

Static files are gathered with collectstatic, then served directly from disk by Nginx or Traefik at high speed, bypassing the Python layer.

User uploads live on a persistent volume or S3-compatible object storage, outside your Git repository — they are never overwritten or removed during code deployments.

Starter includes email support during EU business hours (Mon–Fri, 09:00–17:30 CET) with a target response within one business day. Business adds priority same-day response (typically within 4 business hours) plus automated 24/7 uptime monitoring for critical outages.

Monitoring continuously checks server, web-server and database health. If an incident occurs our team is alerted immediately to restore services; Business subscribers get proactive notifications and status reports.

Raise a request through the client portal or from your account email. Include your app identifier, deployment logs and any error messages so we can help quickly. Contact us →

Starter gets automated daily snapshots of the database and media, retained for 7 days. Business adds higher-frequency backups, 30-day retention and offsite replication within EU data centres.

Push the previous version again. In your project: git revert the change you want undone, then git push as usual. We build and release it the same way, so you are back on the working version within a couple of minutes.

On Business plans we run periodic restore simulations to confirm database dumps rehydrate cleanly in an isolated test environment.

Your app runs in its own container behind a reverse proxy that handles the web address and the Let's Encrypt certificate. You do not choose or maintain any of it.

As soon as your custom domain points to your Technovize IP, we issue a Let's Encrypt certificate automatically and renew it in the background ahead of expiry.

Yes. Starter and Business support background task queues. We provision managed Redis and configure systemd or Docker services to run Celery workers and Beat schedulers alongside your web app.

We handle host-level kernel patches, web-server updates and security hotfixes during low-traffic windows. You're notified in advance if a critical patch needs a brief reboot.

Data is hosted exclusively in EU data centres, and a pre-signed DPA is available in the client portal.

Swap space, Gunicorn worker limits and resource throttling protect the host, and you get alerts when usage is high so you can upgrade before it bites.

Ask us. There is no server login, so send us the command you need — for example createsuperuser — and we run it against your app.

Port 25 is blocked to prevent spam. Use a transactional provider (SendGrid, Mailgun, Postmark) via API or ports 587/465.

Yes — tell us which system libraries your app needs and we install them on the host or add them to your container image.

Sensible defaults are set at the reverse proxy; if you handle large uploads or long requests we tune client_max_body_size and timeouts to avoid 413 and 504 errors.