Install on cloud providers

If you would rather not manage Postgres or SpiceDB yourself, the cloud install templates wire Cuitty to managed equivalents on your provider of choice.

AWS

The AWS reference uses:

• App Runner for the portal container
• RDS Postgres 16 for auth metadata
• EFS for libSQL data
• VPC peering to your existing subnets

A Terraform module is published at https://gitlab.com/cuitty/terraform-aws-cuitty.

module "cuitty" {
  source = "gitlab.com/cuitty/terraform-aws-cuitty"

  vpc_id            = aws_vpc.main.id
  private_subnet_ids = aws_subnet.private[*].id
  domain            = "cuitty.example.com"
}

GCP

The GCP reference uses Cloud Run, Cloud SQL, and Filestore. The Terraform module is at https://gitlab.com/cuitty/terraform-gcp-cuitty.

Azure

Container Apps + Azure Database for PostgreSQL. Terraform module at https://gitlab.com/cuitty/terraform-azure-cuitty.

Fly.io

Fly.io is the simplest managed-but-not-our-cloud option. A fly.toml template lives in the cuitty repo at deploy/fly/.

fly launch --copy-config --from deploy/fly/fly.toml
fly postgres create
fly postgres attach <name>
fly deploy

Cuitty Cloud

If you want zero-ops, Cuitty Cloud is the official managed offering on top of the same OSS core.