Read
Keep your customer’s data current with incremental reads, historical backfill, and on-demand reads.
Write
Create, update, or delete records, with per-field settings and defaults.
Subscribe
Real-time notifications when a record is created, updated, or deleted in your customer’s system.
Search
Find exactly the records you need by field value, with results returned right away.
Proxy
Call any endpoint directly. We handle auth and help with rate limits.
How Ampersand works
1
Define an integration
Use an
amp.yaml file to declare each integration: the system to connect to, the objects and fields to read or write, and the configuration options to expose to your customers. See the manifest reference.amp.yaml
2
Let customers connect and configure
Embed authentication and configuration in your product with prebuilt UI components, headless UI library, or API. Customers connect their own instance and choose field mappings and preferences, and Ampersand saves those choices in their installation.
3
Ampersand runs it
A managed runtime tracks every customer’s configuration and makes the right API calls for each one. It handles authentication, scheduling, retries, rate limits, and non-standard provider error messages. You can either make direct API calls or have async results delivered to your destinations.
4
Monitor, adapt, and recover
Inspect installations and operation logs, get notifications about connection issues, sync failures, and configuration changes, and watch for schema changes when fields are added, removed, or modified. Use these signals to operationalize your integrations by alerting your team or your customers when actions need to be taken.
Built for user-facing integrations
Ampersand handles multi-tenancy at scale. Say you have 400 customers on Salesforce. Every one of them has customized it to reflect how they run their business, with different custom objects, fields, permissions, and rules for how your product interacts with their data. Two very similar companies can store the same data in completely different places. Ampersand separates the integration you build from each customer’s configuration. You define the schema and actions your application needs once, and each installation keeps track of the per-customer mappings. For example, you definerenewalDate once, and each customer uses the embeddable UI library to map it to where they’re actually storing the renewal date in their Salesforce.


Your application reads and writes
renewalDate. Ampersand translates it to each customer’s field.
Watch demo
Get started
Start with code
Clone the starter project and run a working HubSpot, Salesforce, or GitHub integration.
Start with AI
Let Claude Code or another coding agent add integrations to your existing codebase.
Dig deeper
Integration directory
Find the system you want to connect to and how to set it up.
Concepts
How integrations, installations, and configs fit together.
Manifest reference
Everything you can put in
amp.yaml.UI Library
Use our prebuilt components, or go headless to build your own UI.
REST API
Read, write, search, proxy, and manage installations from your backend.
CLI
Deploy and manage your integrations from the terminal.

