Deploy Omega from the console

After you create a sync policy and download a bundle from the Golain console, deploy the Omega agent on your device. The agent runs the sqlite-replication module and connects to Golain over MQTT. Repository: golain-io/omega-rs

Architecture

Console owns policy definition and packaging. Omega agent owns runtime replication — watching the source database, publishing batches, and listening for cloud control messages. Golain cloud owns materialization — lineages, schema reviews, and mirror tables appear in the console after ingest.

Prerequisites

Completed Omega console setup — policy attached, bundle downloaded
Network path to the MQTT broker (TLS or QUIC per your certificate)
Application SQLite database on the device

Step 1 — Download the Omega binary

Unzip the console bundle on the device.
Open OMEGA_DOWNLOAD_URL.txt and download the binary for your selected channel (stable, latest, or dev) and architecture.
Make it executable:

chmod +x omega-agent

You can also build from source: cargo build --release -p omega-agent in the omega-rs repository.

Step 2 — Place certificates

Copy certificate files to the paths referenced in omega-config.yaml. The console bundle defaults to:

./certs/ca.crt
./certs/device.crt
./certs/device.key

Step 3 — Configure the source database path

Edit omega-config.yaml and set sqlite-replication.source_db_path to your application’s SQLite file:

sqlite-replication:
  source_db_path: "/var/lib/myapp/data.db"
  state_db_path: "/var/lib/omega/state.db"

Default paths in the bundle are /var/lib/omega/source.db and /var/lib/omega/state.db. Create the directories if needed.

Step 4 — Start the agent

./omega-agent --profile omega-config.yaml

For development from source:

cargo run -p omega-agent -- --profile omega-config.yaml

For production, install as a systemd service and point the unit at your config path. → Deploy Omega

Generated config reference

A typical console-generated config:

name: my-edge-device
connection:
  transport: mqtt
  server_url: "ssl://mqtt.example.golain.io:8883"
  device_id: "device-uuid-here"
  root_topic: "devices/acme/my-edge-device/device-data"
  mqtt:
    keep_alive: 30s
    clean_session: false
    tls:
      ca_cert_path: "./certs/ca.crt"
      client_cert_path: "./certs/device.crt"
      client_key_path: "./certs/device.key"
modules:
  required: [sqlite-replication]
security:
  max_payload_bytes: 262144
  capabilities:
    sqlite-replication: true
sqlite-replication:
  source_db_path: "/var/lib/omega/source.db"
  state_db_path: "/var/lib/omega/state.db"
  flush_interval: 5s
  snapshot_on_first_run: true
  table_strategies:
    device_state:
      strategy: rows
    sensor_readings:
      strategy: telemetry
      ts_column: recorded_at
      include_columns: [value, unit]

Agent modules enabled by the bundle

Module	Role
sqlite-replication	Watches the source SQLite file, captures changes, flushes to MQTT

Online/offline status is driven by the MQTT session keepalive (the broker tears down a session at ~1.5× connection.mqtt.keep_alive with no traffic), so no separate liveness module is needed. → Full field reference: Configuration

MQTT topics

Topics are prefixed with connection.root_topic from the bundle. Example root: devices/acme/edge-01/device-data

Direction	Topic suffix	Purpose
Device → Cloud	`sync/rows/batch`	Row-level INSERT/UPDATE/DELETE batches
Device → Cloud	`sync/telemetry/batch`	Time-series batches
Device → Cloud	`sync/schema/observe`	Schema fingerprint on change
Device → Cloud	`sync/ingest/request`	Request presigned URL for large uploads
Cloud → Device	`sync/ingest/control`	Pause, resume, state write, URL grant
Device → Cloud	`sync/ingest/ack`	Acknowledge control messages

→ Topics and connection · Downlink control

Step 5 — Verify

Fleet & Devices — device status shows connected.
Omega → Governance → Lineages — one lineage per replicated table.
Schema Reviews — approve queued reviews for new tables. → Schema review workflow
Query data — after approval, use dashboards or the API. → Querying synced data

Troubleshooting (agent)

Problem	Likely cause	Fix
Agent won’t start	`source_db_path` missing or wrong	Point to a real SQLite file
`rows` table silent	No primary key	Add a PK to the table
No telemetry	Wrong `ts_column`	Fix in sync policy; re-download bundle if needed
Changes not detected	App not committing writes	Ensure SQLite transactions commit
Stale data after DB swap	Expected behavior	Agent detects file replacement and re-snapshots
Cloud writes ignored	Table lacks PK	`state_write` requires primary keys

Verification checklist

Agent connected (check logs / device status in console)
MQTT ACL allows publish on {root}/sync/# and subscribe on {root}/sync/ingest/control
Source DB is receiving writes
Internal __omega_journal table exists after bootstrap — do not modify
Console Lineages shows entries for configured tables
Schema reviews appear when schema changes

Internal tables (do not replicate)

The agent creates and manages these. Console schema upload excludes them automatically:

__omega_journal, __omega_journal_seq — change capture
__omega_db_instance — database swap detection

→ Troubleshooting

Alternative: build and configure by hand

If you prefer to build the binary and write the profile yourself rather than download a console bundle, see Omega setup for SQLite sync — it covers the sqlite-replication module and its config section end to end.

Omega in the console

Create policies, attach devices, download bundles.

Capture strategies

Rows vs telemetry vs ignore in depth.

Provisioning checklist

Pre-flight checklist before first sync.

Omega edge runtime

Device RPC

Edge SQLite sync

Edge agent (Omega)

Operate & query

Wire protocol reference

Deploy Omega from the console

Architecture

Prerequisites

Step 1 — Download the Omega binary

Step 2 — Place certificates

Step 3 — Configure the source database path

Step 4 — Start the agent

Generated config reference

Agent modules enabled by the bundle

MQTT topics

Step 5 — Verify

Troubleshooting (agent)

Verification checklist

Internal tables (do not replicate)

Alternative: build and configure by hand

Omega in the console

Capture strategies

Provisioning checklist

​Architecture

​Prerequisites

​Step 1 — Download the Omega binary

​Step 2 — Place certificates

​Step 3 — Configure the source database path

​Step 4 — Start the agent

​Generated config reference

​Agent modules enabled by the bundle

​MQTT topics

​Step 5 — Verify

​Troubleshooting (agent)

​Verification checklist

​Internal tables (do not replicate)

​Alternative: build and configure by hand

​Related

Omega in the console

Capture strategies

Provisioning checklist

Architecture

Prerequisites

Step 1 — Download the Omega binary

Step 2 — Place certificates

Step 3 — Configure the source database path

Step 4 — Start the agent

Generated config reference

Agent modules enabled by the bundle

MQTT topics

Step 5 — Verify

Troubleshooting (agent)

Verification checklist

Internal tables (do not replicate)

Alternative: build and configure by hand

Related