Concepts
| Term | Meaning |
|---|---|
| Project | Isolation boundary (e.g. staging, prod) with members, runtimes, connections, pipelines and policies |
| Runtime | Where connectors run: a Kubernetes namespace or a Docker host, directly or through an agent |
| Connection | A reusable source (PostgreSQL, MySQL/MariaDB, SQL Server, MongoDB, Oracle, CockroachDB, Vitess, Google Cloud Spanner) or destination (Kafka, HTTP, Pub/Sub, Kinesis, Redis Streams, NATS JetStream, Apache Iceberg, PostgreSQL / MySQL / MariaDB / SQL Server through JDBC, Amazon SQS, Amazon SNS, Azure Event Hubs, Apache Pulsar) |
| Pipeline | One source → one destination, the tables, format, transforms and settings. Every saved change is a version; deploying runs one version |
| Health | Healthy · Lagging · At risk (source impact) · Down · Unknown. Never green without fresh evidence |
Admin is account-wide: Admins open every project with every permission and are the only ones who see Settings (people, projects, runtimes, Debezium versions, policies). Everyone else gets a role per project: Viewer, Operator (pause/resume, preview data) or Editor (create, deploy and upgrade pipelines and connections); "Can approve" is a separate per-project right. Everyone has Account (user menu) for their name, theme (System, Light or Dark, also in the user menu), Guided/Expert mode, notifications and personal API tokens. Long lists show 20 rows a page; the rows-per-page choice under each list (10 to 100) applies to every list in that browser. Help & tour (bottom of the sidebar) opens the Tour (what BeziSync does across a pipeline's life, what to try in the project, and what Admins get; its closing "Would your team use BeziSync?" answer reaches the Admins as feedback), Getting started, Learn (Debezium terms in plain words) and search. New members see a dismissible "New here?" card until they open the Tour.