Subprocessors

Cira is built on other people’s infrastructure, and you should know whose before you put your company’s software on it. This list changes when what Cira runs on changes.

• Google Cloud

  United States (us-central1)

  Runs every deployed app, builds them, stores their images and their logs.

  Your apps' code, their environment values, and whatever they log or store.

• Vercel

  United States

  Serves Cira itself.

  Requests to Cira, and its server logs.

• Neon

  United States (AWS us-east-1)

  Cira's database, and the databases Cira makes for apps that ask for one.

  Companies, people, apps, capabilities, and the records of what ran; and, in a separate project per app, whatever that app stores in its own database.

• Upstash

  United States (Google Cloud us-central1)

  The caches Cira makes for apps that ask for one.

  Whatever an app keeps in its own cache, in a separate database per app.

• Clerk

  United States

  Signs people in.

  Names, email addresses, and sessions.

• Cloudflare

  Global edge

  DNS, and the proxy every app is opened through.

  Requests to your apps in transit.

• Anthropic

  United States

  Reads a repository to describe what its app can do, and answers Ask Cira.

  Source files at deploy time, and the questions people ask with what the apps answered.

• Stripe

  United States

  Takes payment.

  Billing contact and payment details, which Cira itself never sees.

• Resend

  United States

  Sends Cira's email.

  Email addresses, and the contents of invitations and notifications.

• Sentry

  United States

  Collects Cira's own errors.

  Error reports from Cira, with request bodies, cookies and headers removed.

Cira does not store the values of your apps’ environment variables: they pass through on their way to Google and are kept by Google, the same as they would be if you deployed there yourself.