ShoalStack is now

platform201
Batteries Included. Deployment Included Too.

Django Web App Blueprint

Start from a working Django app that serves a page and a JSON API. Gunicorn, static files, and a secure gateway are already wired up, so you can skip straight to building.

Django in Production, Already Wired Up

Django gives you the framework. Getting it online is usually the slow part.

Production servers, static files, allowed hosts, and HTTPS each want an afternoon of setup.

This blueprint hands you a Django app already running on production-grade infrastructure. Deploy it first, then make it yours.

Use this blueprint as:

  • A server-rendered Django website
  • A starting point for JSON APIs
  • A foundation for internal tools and dashboards
  • A template for Python web services
Django Example blueprint card
Gateway node routing traffic to the Django container

A Simple Graph with Room to Grow

platform201 turns cloud infrastructure into a visual graph. Each node is a running service; each line a connection that lets two services talk.

Gateway

Gives your app a public HTTPS address and forwards each request to the container.

Django Container

Runs your Django app with gunicorn on Python 3.14, listening on port 8000.

Page & JSON Endpoints

Serves a hello world page on / and JSON from /api/hello, with a /healthz check for uptime probes.

Static Files with WhiteNoise

Collects static files at build time and serves them from the app, with no separate file host to set up.

Django container with its page, API, and health check endpoints

Websites, APIs, Internal Tools, and More

Use the Django Web App blueprint to launch server-rendered sites, JSON APIs, and data-driven apps on infrastructure you control.

Server-Rendered Websites

Server-Rendered Websites

Render pages with Django templates and serve their static assets from the same app.

JSON APIs

JSON APIs

Expose JSON endpoints to web, mobile, and command-line clients from a single service.

Internal Tools & Dashboards

Internal Tools & Dashboards

Build admin panels and team dashboards that live on your own domain and cloud.

Backends for Frontends

Backends for Frontends

Serve a CORS-ready API to Vite, React, or Next.js frontends running on other origins.

Database-Backed Apps

Database-Backed Apps

Add a Postgres node to the graph and manage your data with Django's ORM and migrations.

Prototypes & MVPs

Prototypes & MVPs

Go from repository to a live URL in minutes, with health checks and a gateway in place.

From Example Code to Your Own Django App

Deploy a working Django app first, then swap in your own code with a visual setup flow that keeps infrastructure and domain routing simple.

1

Deploy the Blueprint

Press Deploy and the Gateway and Django container go live from the pre-loaded example code.

2

Open Your Live App

Your app is up at its platform201.live address. Add /api/hello?name=you to see the JSON endpoint.

3

Add Your Code

In the container, connect a GitHub repo or upload your own Django project in place of the example.

4

Set Your Environment Variables

Add DJANGO_SECRET_KEY and DJANGO_ALLOWED_HOSTS, and keep gunicorn listening on the PORT variable.

5

Add Your Custom Domain

On the Domains page, add a hostname you own, then publish the two CNAME records it gives you at your DNS provider. Once they resolve, your certificate is issued.

6

Publish Updates

Merge future changes to your GitHub branch and hit Deploy to publish them.

After Deployment

Your Django app is now live behind the Gateway, served by gunicorn with its static files handled for you.

Next you might add a Postgres database, a background worker, or a scheduled job. You place each one on the same graph and connect it to your app. The whole setup stays in plain sight.

platform201 connected and the Django app live

Ready to Deploy Your Django App?

Start with a working Django blueprint, connect your repository, and deploy on Google Cloud with gunicorn, static files, and HTTPS handled for you.

Deploy This Blueprint

FAQ

Django 6.1 on Python 3.14, served in production by gunicorn with WhiteNoise handling static files. The versions are pinned in requirements.txt, so you upgrade them on your own schedule.