Local cloud development for teams and CI

Build cloud apps locally. Ship with fewer surprises.

TinyCloud gives developers fast, isolated cloud sandboxes on laptops and in CI. Provision resources, run your app, and validate behavior before anything touches a real cloud account.

GitHub Pages friendlySingle binary + DockerLocal dev, test, and CI
$ docker compose up -d tinycloud api worker

$ terraform apply
Apply complete! Resources:
  tinycloud_resource_group.dev
  tinycloud_storage_account.assets
  tinycloud_keyvault.app
  tinycloud_queue.jobs

$ curl http://localhost:8080/upload
{"status":"queued","blob":"uploads/report.pdf"}
Blob
Key Vault
Queues
Terraform
Local dev
CI pipelines
Terraform
Pulumi
SDK tests
Docker Compose

Cloud workflows without waiting on the cloud

Keep infrastructure, app code, and background workers in one local loop. TinyCloud gives each developer a safe environment with realistic service behavior and repeatable state.

Faster inner loop

Run provisioning, uploads, queue processing, and integration tests on your machine without waiting on remote environments.

🔒

Safer by default

Validate app behavior locally before code, credentials, or infrastructure changes ever reach a shared environment.

🧩

Fits existing tools

Use Docker Compose, Terraform, Pulumi, and SDKs with a workflow that feels familiar to platform and application teams.

How a real team uses TinyCloud

An application team runs TinyCloud next to its API and worker service. The API writes files, reads secrets, and queues work — all locally.

1
Start the stack
Bring up TinyCloud, the API, and the worker with Docker Compose.
2
Provision resources
Apply Terraform or Pulumi against TinyCloud to create local resources for the app.
3
Run the app
The API uploads to Blob, reads secrets from Key Vault, and sends jobs to a queue.
4
Process background work
The worker consumes queue messages and reads files from local storage just like a cloud-connected service would.

Why teams like it

0 shared envsGive each developer an isolated sandbox instead of waiting on a shared dev subscription.
Fast CISpin up ephemeral cloud-like environments inside pipelines for repeatable test runs.
Lower costReduce cloud spend for non-production validation loops and preview environments.
Better debuggingKeep logs, service state, and app behavior close to the code you’re changing.
services:
  tinycloud:
    image: tinycloud/tinycloud:latest
  api:
    build: ./api
    environment:
      BLOB_ENDPOINT: http://tinycloud:4577
      KEYVAULT_ENDPOINT: http://tinycloud:4580
      QUEUE_ENDPOINT: http://tinycloud:4578

Start with the cloud services developers actually need

Focus on the most useful local workflows first: provisioning, storage, secrets, queues, and the runtime endpoints apps already expect.

ARM-style control plane

Provision local resources through Terraform, Pulumi, and API-driven workflows.

Blob storage

Save and fetch files locally with cloud-like behavior for uploads, assets, and reports.

Key Vault secrets

Keep local secrets and environment configuration in one place during development.

Queues

Trigger worker flows and integration tests without depending on a remote broker.

Metadata endpoint

Expose discovery information so cloud-aware tooling can target TinyCloud consistently.

Docker-first runtime

Run everything in a single container or full app stack with Compose.

Snapshots & reset

Restore known-good test states and start fresh when you need deterministic runs.

GitHub Pages docs

Publish docs, guides, and marketing pages as a lightweight static site.

“TinyCloud lets our team validate file uploads, secret lookups, and queue-based workflows locally before a single cloud resource is touched.”

Platform engineer
Example customer story

Quick start

docker run -p 4567:4567 -p 4577:4577   -p 4578:4578 -p 4580:4580 tinycloud/tinycloud

terraform init
terraform apply

curl http://localhost:4577/blob/uploads/report.pdf

Build your next cloud feature locally first

Give every developer a fast, safe sandbox for provisioning, integration testing, and app workflows — with a static site that deploys cleanly to GitHub Pages.