Real-time
Two-way sync
Changes in Amazon Lightsail or Pigment instantly reflect in both systems. No stale data, no manual imports.
Database ⇄ Accounting and finance
Amazon Lightsail to Pigment integration — real-time, two-way sync
Keep Amazon Lightsail and Pigment in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
- SOC 2 and 6 other compliance frameworks
- POC with real engineers in minutes
Adopted by fast-scaling companies moving mission-critical data in real time
Case study
Migrated from MuleSoft
Case study
Migrated from Celigo
Migrated from Heroku Connect
Migrated from Matillion
Case study
Migrated from Fivetran
Case study
Migrated from Celigo
Why teams connect Amazon Lightsail and Pigment
Work with Pigment's financial data straight from Amazon Lightsail: read it with ordinary queries, write to it from your own code, and let Stacksync keep both sides consistent.
Engineers need finance data more often than finance systems make it easy to get: for internal tools, reporting services, or logic that reacts to invoices and payments. Working through the vendor API means rate limits, pagination, and glue code that has to be maintained forever.
Stacksync mirrors Dimension lists, Tables, Scenarios, Data imports from Pigment into Databases, Schemas, Tables, Views in Amazon Lightsail and keeps the two in sync bi-directionally and in real time. Your services read finance records with normal queries against Amazon Lightsail, and rows your code writes or updates flow back into Pigment with validation, so the finance system stays the system of record.
Common use cases
- 01 Push CRM pipeline data (deals, stages, amounts) into Pigment for revenue and capacity planning.
- 02 Export approved budgets and forecasts back to a warehouse or Postgres for downstream reporting.
- 03 Migrate data continuously from a Lightsail database to a larger managed database as an application outgrows the VPS tier.
- 04 Sync a Lightsail-hosted application database with a CRM so customer records match what the app stores.
Common sync patterns
Internal tools without API plumbing
Build dashboards and back-office tools directly on Amazon Lightsail; Stacksync handles the API calls, rate limits, and retries against Pigment.
Write back safely
Updates written to the synced tables in Amazon Lightsail propagate into Pigment, so automations can create or correct finance records without custom integration code.
React to financial events
Changes in Pigment appear in Amazon Lightsail as row changes, so you can trigger downstream logic with the database tooling you already use.
What you can sync between Amazon Lightsail and Pigment
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 | Pigment objects | How this pairing syncs | |
|---|---|---|---|
| Tables Relational tables read from and written to at row level. | Tables Row-based transactional data loaded into models from source systems | 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. | Users and permissions Access controls governing which model areas a sync can touch | Managed Databases is specific to Amazon Lightsail and Users and permissions to Pigment — each maps to any object or custom field on the other side. | |
| Databases Logical databases on the instance that scope a connection. | Applications Planning models organized by domain such as finance, sales, or workforce | Databases is specific to Amazon Lightsail and Applications to Pigment — each maps to any object or custom field on the other side. | |
| Schemas Namespaces used when selecting tables to sync. | Metrics Multidimensional values holding plans and actuals; the main target for inbound data | Schemas is specific to Amazon Lightsail and Metrics to Pigment — each maps to any object or custom field on the other side. | |
| Views Query-backed read-only sources. | Dimension lists Master data like accounts, products, or employees that metrics are sliced by | Views is specific to Amazon Lightsail and Dimension lists to Pigment — 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. | Scenarios Versions such as budget, forecast, and actuals that give exported figures their context | Users and Grants is specific to Amazon Lightsail and Scenarios to Pigment — each maps to any object or custom field on the other side. |
How changes propagate between Amazon Lightsail and Pigment
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.
Amazon Lightsail Pigment Interval-based propagation
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 Pigment through its API, with automatic retries and rate-limit backoff.
Pigment Amazon Lightsail Interval-based propagation
DetectionStacksync polls Pigment for changes on an incremental schedule, reading only records changed since the previous pass. No change feed.
DeliveryEach detected change is applied to Amazon Lightsail as a row-level write, with types converted between the two schemas.
Rate-limit considerations
- Amazon Lightsail: No API-style rate limits; capacity is fixed by the chosen Lightsail bundle.
- Pigment: Subject to the platform's API rate limits.
What ships with Amazon Lightsail ⇄ Pigment
Connect Amazon Lightsail and Pigment for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Amazon Lightsail–Pigment connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Amazon Lightsail or Pigment data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
At scale
Event queues
Handle millions of events per minute without losing a single Amazon Lightsail or Pigment record.
Observability
Monitoring
Track your Amazon Lightsail ⇄ Pigment sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between Amazon Lightsail and Pigment.
How the Amazon Lightsail and Pigment connectors work
Amazon Lightsail
- Integration surface
- MySQL or PostgreSQL wire protocol (SQL) to the managed database endpoint
- Authentication
- Database credentials; public endpoint access must be enabled or a tunnel used
- Change detection
- Polling on timestamp or key columns; log-based CDC depends on engine parameter access, which is more limited than on full RDS
- Capabilities
- read · write
- Rate limits
- No API-style rate limits; capacity is fixed by the chosen Lightsail bundle
Pigment
- Integration surface
- REST-based import and export API
- Authentication
- API keys, issued separately for import and export
- Change detection
- no change feed; syncs run scheduled imports and exports
- Capabilities
- read · write
- Rate limits
- subject to the platform's API rate limits
How it works
How to connect Amazon Lightsail to Pigment — three steps, no code
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.
- 01
Connect your apps
Authenticate Amazon Lightsail and Pigment with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Amazon Lightsail
connected
Pigment
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Amazon Lightsail and Pigment 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.
objects · Amazon Lightsail ⇄ PigmentCustomers 12,480Sales Orders 8,213Invoices 5,902Items 1,344 - 03
Map fields
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Amazon Lightsail PigmentCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Amazon Lightsail and Pigment integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Amazon Lightsail and Pigment: authenticate both systems, choose the objects to sync (such as Amazon Lightsail's Tables and Managed Databases), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Amazon Lightsail: MySQL or PostgreSQL wire protocol (SQL) to the managed database endpoint. Authentication: Database credentials; public endpoint access must be enabled or a tunnel used. Pigment: REST-based import and export API. Authentication: API keys, issued separately for import and export. Stacksync manages authentication, retries, and rate limits on both sides.
-
Pigment: Actuals typically flow in from source systems on a schedule while plans and forecasts are edited inside Pigment, making it primarily a data destination. Amazon Lightsail: Lightsail targets simplified, fixed-price bundles; database configuration options are narrower than full Amazon RDS, which affects how much replication tuning is available. Stacksync's field mapping accounts for these differences between Amazon Lightsail and Pigment 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 Pigment 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 Pigment connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Amazon Lightsail–Pigment integration in-house.
-
Yes — Stacksync ships production-grade connectors for both Amazon Lightsail and Pigment. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
SECURITY
Security teams trust Stacksync
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.
SOC 2 Type II
ISO 27001
HIPAA BAA
GDPR
CCPA
DPF US-EU-UK-CH
→ SECURITY WITH BENEFITS
SSO & SCIM
Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.
Alerts
Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.
Secure connection options
Securely connects to your systems with:
Related integrations
Every pair below is a real-time, two-way sync. Search all 342 integrations available for Amazon Lightsail and Pigment.
Popular · 4 of 342
No integrations match .
