Platform architecture, capability roadmap, and commercial framework — a shareable briefing for sales, customer success, and prospects.
Salesforce stays your system of record. Edge delivers faster documents, payments, booking flows, and operational tools on top.
In platform discussions, teams often ask what Edge means for licensing, upgrade path, commercial implications, and operational impact. This section addresses those questions directly.
Parts of the platform have always operated this way — KTAPI, the engine powering search, pricing, availability, and booking, has been running off-Salesforce since day one. Edge formalises this proven pattern and extends it to the user experience layer.
| Edge Is | Edge Is Not |
|---|---|
| An architecture that makes existing features faster and better — at no additional licensing cost | A paid upgrade for capabilities you already use |
| Also the foundation for genuinely new products — discussed commercially before we build | Bundling new products into existing licensing without discussion |
| Purpose-built services that extend Salesforce | A replacement for Salesforce |
| Gradual, non-disruptive — modules transition behind the scenes | A big-bang migration event |
Nothing. Edge integrates seamlessly into your existing Salesforce environment.
Salesforce manages all user identity, profiles, and permissions. Nothing changes for your admins.
Carries user identity, org context, and permissions. No manual step.
Opens as a tab or panel. Knows who you are, which org you are in, and what you can access. No separate login.
Four forces are driving this architectural evolution.
Salesforce imposes hard ceilings — CPU time limits, heap size, API quotas. When your business grows, these ceilings do not move. Edge removes them.
Lightning pages load inside the Salesforce container with limited layout flexibility. Edge apps deliver modern, responsive, purpose-built experiences.
Salesforce managed package releases follow a 6–8 week cycle. Edge services deploy continuously — fixes and features reach you in days.
Salesforce API limits and storage costs grow linearly with usage. Edge services scale elastically and cost less per transaction at volume.
Not all Edge capabilities are created equal. Here is how we categorise what Edge enables and what it means commercially.
No managed package release cycle. We build and deploy new user experiences in days, not the 6–8 week Salesforce release cadence. You get features sooner.
Edge apps can be embedded in Salesforce, served as standalone portals, white-labelled for trade partners, or offered direct to consumers. The platform is no longer locked to a single surface.
Existing features rebuilt at parity, then expanded. Adopt when ready. We build at parity first so you can switch without disruption, then we extend with richer capability.
Capabilities that never existed on the platform — AI agents, multi-channel booking flows, revenue management, distribution APIs. Genuinely new value.
Four concrete scenarios mapped to adoption patterns and their commercial implications.
LWC wizard, governor limits, 6–8 week release cycle
Purpose-built tool, no limits, ships through BAU
Salesforce-only booking wizard, internal users only
Multi-channel: internal, trade, white-label, D2C
Basic document generation, limited templates
Branded templates, PDF, live preview, email delivery
Not available on current platform
AI content, yield management, distribution APIs, agents
What is already on Edge, what is coming, and what remains on Salesforce today.
| App | What It Does |
|---|---|
| Edge Docs | Branded proposals, quotes, trip documents. PDF generation, live preview, email delivery. |
| Edge Pay | Payment collection — deposits, balances, multi-gateway, FX, payment health. |
| Edge Brief | Departure content preparation for ops teams. |
| Edge Canvas | Dynamic configurable components embedded in Salesforce. |
| Edge Admin | Tenant configuration gateway. Blueprints, templates, OAuth. |
| App | What It Does |
|---|---|
| Edge Journeys | Multi-channel booking flow studio for internal, trade, white-label, and D2C. |
| Edge Operations | Operational workflows — cloning, manifests, vouchers, bulk ops, amendments. |
| Edge Agents | Specialised AI agents — automation, data loading, support triage. |
| Module | Status |
|---|---|
| CRM and Contact Management | Remains on Salesforce. Future decisions made in partnership with customers. |
| Core Data Model | Packages, itineraries, services, departures — Salesforce remains the system of record. |
| Reports and Dashboards | Standard Salesforce reporting continues as-is. |
Timelines are indicative and subject to roadmap prioritisation.
Edge runs on enterprise-grade cloud infrastructure with the same security posture as the API services you already depend on.
A clear, simple model for what is included and what requires new terms.
If Edge replaces or improves a module you already license, there is no additional licensing charge. This is our internal architectural decision. Adoption and configuration are scheduled through your existing BAU engagement.
If Edge enables a capability that genuinely did not exist before, we discuss commercial terms openly before we build.
Platform stability and performance within the scope of your existing licensing is our responsibility. Where we choose to resolve issues through Edge architecture rather than Salesforce, that is our investment decision, not yours.