Trigger backend workflows without Apex callout plumbing.
Send Opportunity, Case, Lead, Contract, or custom-object changes to your application while BeaconRelay manages connectivity, durable intake, retries, and failure state.
Turn Salesforce record changes into reliable, replayable, and verifiable HTTPS webhooks, without writing or deploying Apex transport code.
Three controlled stages replace the fragile chain of listener code, temporary memory, and blind HTTP calls. One event identity follows the payload from source to outcome.
Authorize through a Local External Client App owned by the Salesforce customer.
Commit the event before any outbound request can succeed or fail.
Send to HTTPS, classify the response, and keep working when the receiver cannot.
Inspect attempts, receiver responses, route changes, incidents, cryptographic fingerprints and receipts from one workspace.
Explore delivery mechanics
Retryable failures follow a jittered schedule. Broker failure cannot erase a database-backed event.
Replay cursors resume Salesforce streams and failed deliveries retain their complete attempt trail.
Cryptographic evidence lets customers independently verify what BeaconRelay handled.
Salesforce payloads and captured receiver responses are stored as authenticated AES-256-GCM envelopes. The event inbox shows encrypted-byte metadata, not plaintext. Only the signed-in owner can request an in-product reveal, and every reveal is integrity-checked, rate-limited, returned with no-store, and written to the audit trail.
A shared vendor OAuth app is faster to approve, but it reuses one client-credential boundary across every customer authorization. BeaconRelay rejects that shortcut. Every new station uses a Local External Client App created inside the Salesforce organization whose events it transports.
This does not mean BeaconRelay cannot process authorized events. Transport requires that access. It means the authorization is explicit, scoped to one organization, encrypted per station, and independently controlled by the customer.
Review the Salesforce setupRequired for every new BeaconRelay station. The one-time setup is deliberate security work that keeps customer authorization boundaries independent.
Select the Salesforce objects and operations that matter, connect one HTTPS destination per station, and let BeaconRelay operate the transport path. Your team keeps its code focused on the workflow, not connection management, Apex callouts, replay recovery, or retry schedulers.
Send Opportunity, Case, Lead, Contract, or custom-object changes to your application while BeaconRelay manages connectivity, durable intake, retries, and failure state.
Turn a qualifying Salesforce update into a dependable request to document services, approval engines, or customer onboarding systems without embedding vendor logic in Salesforce.
Provide stable event IDs, delivery history, signatures, and controlled payload access so asynchronous agent work can be correlated, retried, and reviewed.
Route selected changes to ingestion APIs, analytics workers, search indexes, or customer systems without repeatedly polling Salesforce for updates.
A small listener can prove the happy path. Production means owning token refresh, event-stream lifecycle, replay positions, durable queues, retry policy, concurrency, observability, encryption, redrive controls, and evidence every day.
Start with the transport readyBeaconRelay is a focused transport layer between authorized Salesforce event streams and your HTTPS application.
For the BeaconRelay transport path, you configure validated Salesforce objects and operations instead of writing and deploying Apex callout code. BeaconRelay listens to authorized Salesforce event streams, persists each event, and delivers it to your HTTPS receiver.
No. Each station uses a customer-managed Local External Client App for OAuth. There is no BeaconRelay managed package, namespace installation, or shared global Consumer Secret.
The event is already stored before delivery begins. Retryable network and HTTP failures follow a twelve-attempt schedule, preserve every attempt, and end in an explicit Dead Letter state that the owner can redrive.
BeaconRelay delivers to a customer-configured public HTTPS endpoint after URL safety validation. That can be your backend API, integration service, workflow engine, data pipeline, or AI agent gateway.
Payloads are encrypted at rest and concealed in the event inbox. An authenticated owner can request an audited, integrity-checked reveal. BeaconRelay still processes authorized plaintext in memory when receiving and delivering an event; encryption at rest is not end-to-end encryption.
Retries and redrives are included and never counted twice. Every plan includes monitoring, replay, encryption and delivery signatures.
events total
events / month
events / month
events / month
events / month
Core transport behavior is included on every plan. Paid tiers increase event volume, Salesforce organizations, channels, retention, and support.
| Capability | Trial | Startup | Growth | Business | Enterprise |
|---|---|---|---|---|---|
| Price | Free | 19 EUR / month | 49 EUR / month | 199 EUR / month | Custom |
| Access period | 14 days | Monthly | Monthly | Monthly | Contracted |
| Unique events | 2,500 total | 10,000 / month | 100,000 / month | 1,000,000 / month | 5M+ / month |
| Salesforce stations | 1 | 1 | 2 | 5 | Contracted |
| Channels | 1 total | 2 total | 6 total | 15 total | Contracted |
| HTTPS destinations | 1 / station | 1 / station | 1 / station | 1 / station | Contracted |
| Payload retention | 7 days | 7 days | 14 days | 30 days | 90+ days |
| Monitoring and replay | Included | Included | Included | Included | Included |
| Automatic retries | Included | Included | Included | Included | Included |
| Dead Letter redrive | Included | Included | Included | Included | Included |
| Encryption at rest | Included | Included | Included | Included | Included |
| Delivery signatures | Included | Included | Included | Included | Included |
| Support | Documentation | Standard email | Priority email | Dedicated + SLA |
One destination per station. At quota exhaustion, newly received events pause durably; BeaconRelay does not silently discard them. Payload expiry removes content from terminal events while retaining hashes, signatures, receipts and operational metadata.