Skip to main content

Reference

Backend API

Use backend-api when the service can start without a managed database but still needs a clear supported path from first deployment to later growth. In the current DigitalOcean catalog, this is the narrow API baseline before moving into database-backed blueprints.

Current variants

Same scenario, different operating depth. Move from managed runtime toward more control and operational responsibility as the blueprint scales.

DigitalOcean

App Platform

Deploy the API as a single App Platform service with optional managed databases and built-in DNS integration.

Components

App Platform DigitalOcean DNS

Growth boundary

Start here when you want the smallest managed runtime footprint and do not need to operate hosts directly.

Read variant

DigitalOcean

Single Droplet

Run the API on one Droplet with VPC, firewall, reserved IP, DNS, and optional managed database support.

Components

Droplet VPC DigitalOcean DNS Cloud Firewall Reserved IP

Growth boundary

Use this path when the team wants a simple VM baseline and is comfortable owning the host.

Read variant

DigitalOcean

DOKS

Provision a Kubernetes base with load balancing for API workloads that need a cluster-first deployment model.

Components

Kubernetes VPC Load Balancer

Growth boundary

Use this path when the team is already committed to Kubernetes as the operating model.

Read variant

Not the right fit?

If this blueprint is close but not the right starting point, go back to the catalog or compare nearby paths.

Previous

Blueprint Catalog

Next

Web App