Mental Model

Forge is a stateless web layer that sits in front of your Salesforce org. It accelerates event-planning workflows without replacing Salesforce as the place where records actually live.

Salesforce is the system of record

Every record Forge creates or updates — events, attendees, sessions, tickets, speakers, sponsors, forms — is written directly to Salesforce through the standard REST and Composite APIs. There is no Forge-side copy of your data. If you lose your Forge subscription tomorrow, everything is still in your org exactly as you left it.

• Forge's Postgres database stores only operational state: tenant rows, encrypted OAuth tokens, sessions, audience ID lists (no PII), email job definitions, and audit logs.
• Redis holds short-lived hydration caches — attendee display names for roughly two hours, metadata and config for minutes — then auto-evicts everything.
• No customer record data (names, emails, phone numbers, addresses) is ever mirrored to Forge's Postgres.

Just-in-time (JIT) derivation

When a Forge screen needs personal data — an attendee's name, an email address — it fetches it from Salesforce at request time. The value may be held briefly in an encrypted Redis cache to reduce API calls, but it is never written to Postgres and is never logged.

Forge inherits Salesforce permissions

Every API call Forge makes is authenticated as the signed-in Salesforce user. Field-Level Security, sharing rules, validation rules, triggers, and Flows all execute exactly as they do inside Salesforce itself. Forge has no permission layer that can override or bypass your org's configuration.

Deep links to Salesforce records

Every Salesforce-backed surface in Forge displays a Salesforce record icon (the SalesforceLinkIcon) that opens the underlying record in your org in a new tab. This means you can jump from a Forge attendee row straight to the Attendee__c record in Salesforce without leaving your workflow.