Two-way sync
Changes in Amazon Lightsail or Supabase instantly reflect in both systems. No stale data, no manual imports.
Keep Amazon Lightsail and Supabase in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
Two databases that must agree is one of the oldest problems in engineering: different engines for different workloads, separate services with overlapping reference data, a migration in flight, or regional instances that share a subset of records. Hand-rolled replication across systems means change capture, conflict handling, and type mapping, all built and maintained by your team.
Stacksync syncs tables or collections between Amazon Lightsail and Supabase continuously and bi-directionally, translating types between the two engines and resolving conflicts by rules you configure. Rows written on either side appear on the other within seconds.
Mirror selected tables to another region or environment continuously, filtered to just the rows that should travel.
Keep the same dataset live in both Amazon Lightsail and Supabase, so each workload runs on the engine that suits it.
When one database is replacing the other, sync both directions during the transition and switch traffic when ready, without a freeze window.
Representative objects on each side — any object or custom field can map to any target. Schemas are auto-detected; types are converted between the two systems.
| Amazon Lightsail objects | Supabase objects | How this pairing syncs | |
|---|---|---|---|
| Schemas Namespaces used when selecting tables to sync. | Schemas Namespaces (public and custom) that scope sync access. | Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. Custom fields on either side are included in the mapping. | |
| Tables Relational tables read from and written to at row level. | Tables Standard Postgres tables; the primary two-way sync target. | Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. | |
| Views Query-backed read-only sources. | Views Read-side projections exposed to outbound syncs. | Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. | |
| Managed Databases Lightsail-hosted MySQL or PostgreSQL instances that a sync connects to as standard databases. | JSONB Columns Semi-structured payloads such as event properties or nested objects. | Managed Databases is specific to Amazon Lightsail and JSONB Columns to Supabase — each maps to any object or custom field on the other side. | |
| Databases Logical databases on the instance that scope a connection. | Database Functions Postgres functions that can transform or validate synced rows. | Databases is specific to Amazon Lightsail and Database Functions to Supabase — each maps to any object or custom field on the other side. | |
| Users and Grants Database accounts used to give the sync connection scoped access. | Storage Object Metadata File metadata rows that can be joined to synced application data. | Users and Grants is specific to Amazon Lightsail and Storage Object Metadata to Supabase — each maps to any object or custom field on the other side. |
Each direction of the sync is driven by what the source system can signal and what the destination accepts — detection, delivery, and expected latency below.
DetectionStacksync polls Amazon Lightsail for changes on an incremental schedule, reading only records changed since the previous pass. Polling on timestamp or key columns.
DeliveryEach detected change is applied to Supabase as a row-level write, with types converted between the two schemas.
DetectionSupabase pushes changes as they happen — webhook events backed by change data capture. Log-based CDC via Postgres logical replication, the same WAL feed that powers Supabase Realtime.
DeliveryEach detected change is applied to Amazon Lightsail as a row-level write, with types converted between the two schemas.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Amazon Lightsail–Supabase connection.
Changes in Amazon Lightsail or Supabase instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Amazon Lightsail or Supabase data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single Amazon Lightsail or Supabase record.
Track your Amazon Lightsail ⇄ Supabase sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Amazon Lightsail and Supabase.
Configure and sync within minutes, no code. Whether you sync 50k or 100M+ records, Stacksync handles the queues, infra, and plumbing. Integrations are non-invasive and need zero setup on your systems.
Authenticate Amazon Lightsail and Supabase with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Pick the Amazon Lightsail and Supabase objects to sync — Stacksync auto-detects both schemas, including custom fields where the platform exposes them. Sync to existing tables, or let Stacksync create new ones with ideal data types.
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Yes. Stacksync provides a managed, real-time two-way integration between Amazon Lightsail and Supabase: authenticate both systems, choose the objects to sync (such as Amazon Lightsail's Schemas and Tables), map fields visually, and changes propagate both ways in milliseconds — no code required.
Stacksync is SOC 2 Type II and ISO 27001 certified with HIPAA BAA support. Data is encrypted in transit, and a zero-persistent-storage architecture means Amazon Lightsail and Supabase records are not retained after a sync operation.
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Amazon Lightsail and Supabase connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Amazon Lightsail–Supabase integration in-house.
Yes — Stacksync ships production-grade connectors for both Amazon Lightsail and Supabase. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
Change detection on Amazon Lightsail: Polling on timestamp or key columns; log-based CDC depends on engine parameter access, which is more limited than on full RDS. On Supabase: Log-based CDC via Postgres logical replication, the same WAL feed that powers Supabase Realtime; database webhooks can also fire on row changes. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
On the Amazon Lightsail side: Schemas, Tables, Views, Users and Grants, plus custom fields where Amazon Lightsail exposes them. On the Supabase side: Storage Object Metadata, Tables, Views, Schemas. Stacksync auto-detects both schemas and converts types between the two systems.
As a data company, we understand the importance of keeping your data secure. Stacksync is built with security best practices to keep your data safe at every layer, and is DPF-certified for US, EU, UK and CH data transfers.
Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.
Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.
Securely connects to your systems with:
Every pair below is a real-time, two-way sync. Search all 471 integrations available for Amazon Lightsail and Supabase.