Skip to main content

What you’ll build

A product launch page with a working email waitlist. You’ll build it from source, connect a private backend to accept signups, and give it persistent storage so the list survives restarts. Then you’ll follow a signup through the system to see how the pieces work together. A visitor joins the email waitlist on the launch page, the private API accepts the signup, and PostgreSQL stores it. The frontend and API run across AWS and GCP.

Start the series

Follow parts 1–5 in order. Part 6 is optional and requires a domain you own.

1. Deploy your first workload

Create a GVC across AWS and GCP, deploy NGINX, and open it through one global HTTPS endpoint.

2. Deploy your own application

Build the launch page from source, push its image to your private registry, and run it in both locations.

3. Connect two workloads

Deploy a private API and allow the frontend to call it over the internal network to accept waitlist signups.

4. Add a database and secret

Save signups in PostgreSQL and grant the API access to its credentials through an identity, a policy, and a secret reference.

5. Observe your workload

Read logs and metrics, enable tracing, and follow a signup request from the frontend to the API.

6. Configure a custom domain (optional)

Point a domain you own at the frontend, with Control Plane issuing and renewing its TLS certificate.
You need an org to deploy into. If you don’t have one yet, sign up for Control Plane: the Console walks you through creating a billing account and your first org.