Appendix
Vocabulary
Industry terms and what they map to here
Standard infrastructure terms and what each one maps to on Remy.
| Industry term | On Remy |
|---|---|
| Tenant | A workspace: the billing and permission boundary that owns apps. Each workspace has members, settings, a storage region, and its own vendor controls. |
| Application | An app: a git repository with a manifest, methods, tables, and interfaces, owned by a workspace. |
| Deployment, version | A release: one immutable build of one commit, with a status of building, compiled, live, preview, failed or superseded. |
| Production | Live: the release the app's pointer names. |
| Staging environment | There is no shared staging. A preview is a per-branch release on its own data; dev is a per-person environment on its own data. |
| Function, endpoint, handler | A method: a TypeScript function in the app's backend contract, invoked through any interface. |
| Serverless | Not quite. A method runs in a release sandbox: a persistent Kata microVM assigned to a release, kept warm, and reused across invocations. Cron and email runs use disposable sandboxes that exit after one execution. |
| Container | A sandbox: a Kata microVM, which is a container inside a lightweight VM with its own kernel. |
| Cold start | A queued claim: no warm sandbox was available and the caller waited for the pool to fill. A warm claim takes tens of milliseconds. |
| Snapshot | Three different things: a workspace snapshot is a dev box's home directory saved to S3; a database mirror is a jewel run's pre-action copy of a database; a backup snapshot is AWS Backup's daily copy of the platform database. |
| Migration | Two different things: an app schema change, applied to a clone of the app's database at build and promoted atomically; and a platform migration, raw SQL applied to the platform database by a Job before every rollout. |
| Rollback | Re-promoting a prior release, or a git revert that builds a new one. |
| Blue/green, canary | The pointer swap at promotion is the cutover; requests in flight finish on the old release. Node groups roll blue/green. |
| Region | A region slug such as us-1 or eu-1: the workspace's chosen home for its data at rest, mapped to an AWS region. |
| Data residency | Data at rest in the workspace's region. Compute runs in one region; the hot working copy is checkpointed back to the home region hourly. |
| VPC | Two of them: the trusted VPC for the platform, and the untrusted VPC for app code. |
| Cluster | Two EKS clusters, one per VPC. |
| Worker | Two meanings: a worker role pod that drains SQS queues, and the release worker process inside a sandbox that runs methods. |
| Secret | An app secret (the builder's, KMS-encrypted, injected into the sandbox), an operator credential (the platform's vendor keys), or a workspace key (a workspace's own vendor key). |
| Service account | A Kubernetes ServiceAccount mapped through Pod Identity to an IAM role. Sandboxes have none. |
| Vendor, subprocessor | A counterparty: a legal entity in the registry. A surface is one credential and one egress flow to it. |
| SIEM export | The audit log's OCSF export. |
| CDN | Cloudflare Workers over the public buckets, plus per-region CloudFront distributions for signed private files. |
| Custom domain | A Cloudflare for SaaS custom hostname, with the certificate issued and renewed by Cloudflare. |
| Embedding | An app declaring frame-ancestors origins; not embeddable by default. |
| SSO | Two meanings: WorkOS SSO for workspace members, and Sign in with Remy, delegated sign-in to an app for the owning workspace's members. |
| API key | A workspace API key (sk_) for the platform, or a per-user app API key for an app's API interface. |
| Fine-tuned model | A jewel's trained adapter, served from the platform's own vLLM pool under an id that names the app and method. |
| Vector database | Qdrant: a shared pool of tenants, or a dedicated instance provisioned per customer resource. |
| Warm pool | The orchestrator's global pool of pre-booted sandboxes, sized by a queueing model, with reserved and shared tiers. |
| Island | One of the three untrusted node groups: kata_apps, kata_jobs, kata_dev. |
| Dev box | The editor's leased microVM with the full development image. |
| Tunnel | The CLI's dev session that routes a person's dev invocations to their own machine. |
| Hook token | The per-execution credential a sandbox presents on every callback. |
| Callback origin | The one public hostname a sandbox reaches back on. |