Skip to content

What is Comwit Cloud?

Comwit Cloud is a project workspace behind one product API and console. Instead of stitching together a database, object storage, app runtime, and DNS provider yourself, you work with all four from a single place — a web console, a comwit CLI, or a public HTTP API — with access scoped to your project.

If you have never used Comwit Cloud before, this page explains what it is and how its pieces fit together. Later pages show the exact commands.

Everything you build lives inside a project. A project groups its databases, Storage resources, repositories, apps, and domains together, and your access is scoped per project. Within a project:

  • Databases — Turso/libSQL databases (powered by Louhi), reachable at https://db.cloud.comwit.io. You can create a database, connect to it, run SQL, rotate its tokens, and view usage.
  • Runtime apps — Next/V8 isolate apps (powered by brrrd). You can create an app, deploy a build, set environment variables, roll back to a previous build, and attach hostnames.
  • Storage — S3-compatible object buckets backed by R2. Use a standard S3 client with project credentials, or serve public assets directly through a stable *.comwit.link URL.
  • Repositories — create project Git repositories in the console, then clone and push over HTTPS. Repositories.
  • Project domains & DNS — bring a domain you already own under Route 53 delegated DNS, manage its records, and attach hostnames to your runtime apps.

A project is the top-level container. Under it:

  • A database is a libSQL database, identified by a database_id and reached through a database_url. Its access tokens are returned to you once, at create or rotate time, and are never stored by Comwit — so save them when you see them.
  • An app is a deployable runtime application, identified by an app_id. Each deploy produces a build (a build_id), and the active build is the one serving traffic.
  • A project domain is a domain you own that has been onboarded for delegated DNS, so Comwit can manage its Route 53 records on your behalf.
  • A runtime app hostname is a hostname attached to one app. It comes in two flavors: Manual DNS, where you publish the returned records yourself, and Automatic DNS, where Comwit writes the records into a project domain’s Route 53 zone for you.
  • A Storage resource is a project-owned S3-compatible bucket with an authenticated S3 endpoint and optional direct public base URL.

You authenticate with a token — a cwt_<hex> personal token for developers or a cwp_<hex> project token for deployed services, constrained by scopes and project ownership. See Concepts for the full glossary.

There are three surfaces, and they all sit in front of the same public platform API. Pick whichever fits the task.

SurfaceHostBest for
Web consolehttps://cloud.comwit.ioInteractive use, SQL console, first-time setup
comwit CLIcalls api.cloud.comwit.ioDay-to-day dev, deploys, scripting
Platform APIhttps://api.cloud.comwit.ioAutomation, CI, custom integrations

The CLI and console both call the same public platform API. Anything the CLI can do, you can also do with a raw HTTP call using a token — so you can start in the console, automate with the CLI, and integrate directly against the API as your needs grow.

A few platform behaviors are worth knowing before you dig in:

  • App environment variables are plain values only. Marking a variable as secret: true is rejected, because Secrets Manager is not enabled for app environment variables.
  • Delegated DNS for a domain you already own is live. Buying a domain through a registrar is planned, not yet live.
  • Quickstart — go from a token to a database, an app, and a domain, end to end.
  • Install the CLI — set up the comwit CLI for day-to-day work.
  • Concepts — projects, databases, Storage, apps, domains, hostnames, and tokens explained in one place.