Gateway Destinations: Writing to On-Premises Databases
Learn how to use BEEM Gateway Destinations to push data from your BEEM warehouse to on-premises databases such as Microsoft SQL Server, on a scheduled or on-demand basis.
Gateway Destinations let you push data from your BEEM warehouse to on-premises databases that are not directly accessible from the cloud. The BEEM Gateway agent, deployed inside your network, acts as a secure bridge to write processed data back to your local database systems.
Availability
Gateway Destinations is available on Pro and Enterprise plans.
Supported Destinations
- Microsoft SQL Server
- PostgreSQL (available upon request)
- MySQL (available upon request)
How It Works
- Full refresh: Each scheduled run replaces the target table contents with the latest data from BEEM
- Incremental (where supported): Only new or changed rows are written, reducing transfer time
- The gateway agent handles connectivity — no inbound firewall rules are needed on your network
- Scheduling supports daily, hourly, or custom cron expressions
Gateway Destinations vs Flows
| Feature | Gateway Destinations | Flows (Reverse ETL) |
|---|---|---|
| Target type | On-premises databases behind firewalls | Cloud-based SaaS tools and APIs |
| Connectivity | BEEM Gateway agent behind firewall / VPN | Direct API integration |
| Best for | Writing to internal SQL databases | Pushing data to CRMs, marketing tools, etc. |
| Table management | BEEM creates and manages target tables | Mapping defined per flow |
Key Details
- Requires a BEEM Gateway agent deployed in your network
- Target table schemas are created and maintained by the BEEM team
- DPU usage is tracked for each destination sync
- The BEEM team manages scheduling and monitors sync health
For technical installation and configuration details, see BEEM Gateway: Installation and Configuration.
Updated 2 months ago