Platform Architecture for Delivery
Understanding Core and Edge — what delivery teams need to know about the two-layer architecture.
Overview
Kaptio’s platform has two architectural layers. Delivery teams need to understand which layer they are working with because the tooling, deployment process, and governance differ.
Core (Salesforce)
What it is: CRM, inventory, pricing, rules, suppliers. Enterprise-grade, stable, trusted.
Delivery relevance:
- Most customer data and business logic lives here
- Configuration uses Salesforce metadata, custom objects, and the Kaptio managed package
- Deployments go through Salesforce DX / SFDX tooling
- Changes require understanding of Kaptio’s Apex APIs (KaptioQueryV2, KaptioUowV1, etc.)
- Testing follows Salesforce unit test requirements (75% coverage minimum)
Key systems: Packages, Inventory, Tour Builder, Pricing Engine, Payments (auto-pay), Supplier Management.
Edge (Kaptio-controlled, GCP)
What it is: Document engine, payments, booking surfaces, persistence API, event stream. Built for product velocity on infrastructure Kaptio controls.
Delivery relevance:
- Document templates and tenant configuration (YAML, Handlebars, JSON schemas)
- Payment gateway integration (Braintree, Stripe via Utopaya)
- Booking surfaces (Quest, Voyage)
- Ecommerce API integration
- Configuration lives in
edge-doc-engine-configsrepo (separate from application code)
Key systems: Edge Docs (Editor, Viewer, Render Engine), Edge Pay, Quest (enquiry portal), SmartSave.
Why This Matters for Delivery
| Aspect | Core | Edge |
|---|---|---|
| Configuration | Salesforce metadata + managed package | YAML blueprints + Handlebars templates |
| Deployment | SFDX → Salesforce orgs | GitLab merge → GKE (auto) or Netlify |
| Testing | Apex unit tests + UAT in sandbox | Browser testing + API testing |
| Tenant isolation | Salesforce org boundaries | Tenant ID in config + JWT auth |
| Change control | SF deployment pipeline | Config repo merge requests |
Go-live checklists should always specify which layer — a Core go-live checklist is different from an Edge go-live checklist.
Product Experiences
The platform delivers six product experiences across the two layers:
| Experience | Layer | Description |
|---|---|---|
| Voyage | Core + Edge | Itinerary and booking |
| Quest | Edge | Enquiry portal and itinerary builder |
| Circle | Core | Group travel management |
| Docs | Edge | Document generation and editing |
| Pay | Edge | Payment collection |
| Canvas | Edge | Workflow automation (experimental) |