Gateway Destinations: Writing to On-Premises Databases

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)

Ensure Gateway Connectivity

A BEEM Gateway agent must be deployed inside your network (see the Database Bridge article for agent installation)
The agent must have network access to the target database
Verify the target database accepts connections from the machine running the gateway agent
Ensure the required port is open (e.g., 1433 for SQL Server, 5432 for PostgreSQL)

Prepare the Target Database

Create a dedicated database or schema for the replicated data
Create a service account with write permissions on the target schema
The BEEM team will create the target tables during configuration — no manual table creation is needed
Ensure adequate storage for the expected data volume

Contact BEEM for Configuration

Contact [email protected] or your BEEM account manager
Provide:
- Target database type and version (e.g., SQL Server 2019)
- Host, port, and service account credentials
- Target schema or database name
- List of source tables or datasets to replicate
- Desired schedule (e.g., nightly, hourly, custom cron)
The BEEM team configures the gateway destination and creates the target tables

Validate the Replication

The BEEM team triggers an initial sync to populate the target tables
Verify data in your on-premises database matches expectations
Confirm the automated schedule is running as configured
Monitor execution status in the Monitor section of BEEM

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.