Two-way sync
Changes in Amazon Lightsail or Kustomer instantly reflect in both systems. No stale data, no manual imports.
Keep Amazon Lightsail and Kustomer in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
Product and engineering teams constantly need CRM data, and the CRM API is a poor way to get it: rate limits, pagination, custom objects, and integration code that breaks when an admin renames a field. What they actually want is the data in Amazon Lightsail, where it can be queried and joined like everything else.
Stacksync mirrors Notes, Customers, Conversations, Messages from Kustomer into Views, Users and Grants, Managed Databases, Databases in Amazon Lightsail with real-time, bi-directional sync. Read CRM records with plain queries; write updates from your application and they appear in Kustomer with validation intact. Go-to-market teams keep working in the CRM, engineers keep working in the database, and neither has to think about the other.
Back-office apps read and write the synced tables; Stacksync handles the Kustomer API, limits, and retries.
Field and stage updates in Kustomer arrive as row changes in Amazon Lightsail, ready to drive jobs and notifications.
Accounts, contacts, and custom objects from Kustomer become tables in Amazon Lightsail you can join with application data directly.
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 | Kustomer objects | How this pairing syncs | |
|---|---|---|---|
| Databases Logical databases on the instance that scope a connection. | Companies Organization records group customers and map to CRM accounts. | Databases is specific to Amazon Lightsail and Companies to Kustomer — each maps to any object or custom field on the other side. | |
| Schemas Namespaces used when selecting tables to sync. | Custom Objects (Klasses) Structured external records such as orders and subscriptions synced in to appear on the customer timeline. | Schemas is specific to Amazon Lightsail and Custom Objects (Klasses) to Kustomer — each maps to any object or custom field on the other side. | |
| Tables Relational tables read from and written to at row level. | Users Agent records map conversation ownership to people in other systems. | Tables is specific to Amazon Lightsail and Users to Kustomer — each maps to any object or custom field on the other side. | |
| Views Query-backed read-only sources. | Teams Team assignments support routing parity and reporting. | Views is specific to Amazon Lightsail and Teams to Kustomer — 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. | Tags Labels on conversations and customers sync for categorization and analytics. | Users and Grants is specific to Amazon Lightsail and Tags to Kustomer — each maps to any object or custom field on the other side. | |
| Managed Databases Lightsail-hosted MySQL or PostgreSQL instances that a sync connects to as standard databases. | Notes Internal annotations carry context alongside synced conversations. | Managed Databases is specific to Amazon Lightsail and Notes to Kustomer — 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 written to Kustomer through its API, with automatic retries and rate-limit backoff.
DetectionKustomer notifies Stacksync of record changes through webhook events. Outbound webhooks on record events, plus polling for backfill.
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–Kustomer connection.
Changes in Amazon Lightsail or Kustomer instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Amazon Lightsail or Kustomer 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 Kustomer record.
Track your Amazon Lightsail ⇄ Kustomer sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Amazon Lightsail and Kustomer.
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 Kustomer 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 Kustomer 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 Kustomer: authenticate both systems, choose the objects to sync (such as Amazon Lightsail's Databases and Schemas), map fields visually, and changes propagate both ways in milliseconds — no code required.
Kustomer: Custom object types are called Klasses, and they are the standard mechanism for landing external data like orders and subscriptions where agents work. Amazon Lightsail: External access requires enabling the database's public endpoint or routing through a Lightsail instance, which determines how a sync platform reaches it. Stacksync's field mapping accounts for these differences between Amazon Lightsail and Kustomer without custom code.
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 Kustomer 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 Kustomer connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Amazon Lightsail–Kustomer integration in-house.
Yes — Stacksync ships production-grade connectors for both Amazon Lightsail and Kustomer. 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 Kustomer: Outbound webhooks on record events, plus polling for backfill. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
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 351 integrations available for Amazon Lightsail and Kustomer.