# Fogpipe Cloud

> Fogpipe Cloud is a European PaaS: deploy container apps to HTTPS URLs with
> managed Postgres, object storage, custom domains, and GCP-style IAM — via the
> fpcloud CLI, a REST API, and an OpenTofu/Terraform provider. All data stays
> in the EU. The CLI prints an LLM-dense reference of every command and flag
> with fpcloud --help-llm.

## Guides

- [Quickstart — deploy a container](/docs/md/quickstart.md): Deploy your first container to Fogpipe Cloud — from login to a live HTTPS URL, plus Postgres, config, logs, and a custom domain.
- [Off-site database backup mirror — setup howto](/docs/md/backup-mirror-setup.md): Mirror a managed database's backups to your own AWS S3 or GCS bucket, keyless via OIDC — no access keys stored anywhere.
- [Billing](/docs/md/billing.md): See what your organization is spending — fpcloud billing reports the cost of the period in progress and the invoices for closed periods, and manages who is allowed to see them.
- [GitHub Actions Runners](/docs/md/ci-runners.md): Run GitHub Actions on your own project — fpcloud runner creates a pool of ephemeral runners, one pod per job, that workflows opt into with runs-on.
- [CLI & OpenTofu Experience](/docs/md/cli-and-terraform.md): The full fpcloud CLI surface (auth, apps, databases, domains, config, IAM, registry) and the OpenTofu/Terraform provider that mirrors it 1:1.
- [Database Backups](/docs/md/database-backups.md): Automated Postgres backups — set a schedule and a recovery window, restore to a point in time, and check that the backups are actually producing restore points.
- [Database Extensions](/docs/md/database-extensions.md): Install a Postgres extension in a managed database — which ones are curated, why the platform installs them for you, and what changes for your migrations.
- [Deploy to Fogpipe Cloud from GitHub Actions](/docs/md/deploy-from-github.md): Push-to-deploy from GitHub Actions with no stored secrets — OIDC federation, project-scoped registry push, and gated release commands.
- [Projects, namespaces & access](/docs/md/projects-and-access.md): How projects, identities, IAM, and managed databases work on the fpcloud control plane — who can do what, and how to reach a database.
- [Scheduled Jobs](/docs/md/scheduled-jobs.md): Run work on a schedule — fpcloud job schedules an HTTP call to your own app or a container run, with timezones, overlap policy, retries, manual triggers and run history.
- [Object Storage](/docs/md/storage.md): S3-compatible object storage per project — buckets, scoped keys, app binding, the fps:// data-plane CLI, quotas, object expiry, and static-site serving.
- [Terraform / OpenTofu remote state in an fpcloud bucket](/docs/md/terraform-remote-state.md): Store Terraform/OpenTofu state in an fpcloud bucket via the standard s3 backend, with real state locking through use_lockfile.
- [Usage](/docs/md/usage.md): See what your workloads consumed — fpcloud usage reports metered CPU core-hours, memory and storage GiB-hours per app, per database and per day, for a project or a whole organization.
- [Static Websites](/docs/md/websites.md): Host static sites with one command — fpcloud website deploy syncs a directory, serves it over HTTPS, and supports SPA mode, vanity slugs, and custom domains.

## API reference

- [OpenAPI specification](/openapi.yaml): the complete REST API contract
- [Interactive API docs](/docs): browsable reference over the same spec

## Optional

- [llms-full.txt](/llms-full.txt): every guide above concatenated in one file