INTEGRATION GUIDES
Choose the integration pattern that fits your product.
Hamiltonn integration guides explain how customer applications, backend systems, webhooks, identity and external providers fit around the platform boundary.
Hamiltonn Cloud
Choose the integration pattern that fits your product.
Hamiltonn Integration Guides are architecture patterns for connecting supported Hamiltonn Cloud services to customer applications and external systems.
Definition
What does this mean?
Hamiltonn Integration Guides are architecture patterns for connecting supported Hamiltonn Cloud services to customer applications and external systems.
Hamiltonn Cloud combines reusable software infrastructure, configurable product capabilities and flexible deployment so organisations can build around their own brand and operating model.
PATTERNS
Common ways to build on Hamiltonn.
Managed + integrations
Use Hamiltonn’s managed UI while synchronising selected systems.
Custom frontend / BFF
Build your own frontend with a secure backend-for-frontend.
Backend-to-backend
Provision, synchronise or report through server-side integrations.
Event-driven
Use webhooks to react to relevant events.
Dedicated API
Connect applications to a dedicated environment.
AI in existing software
Add AI agents or knowledge inside an existing product.
BFF PATTERN
Keep privileged integration logic server-side.
User app
Browser or mobile experience.
Customer backend
Own business-specific logic.
Hamiltonn API
Use protected credentials and tenant context.
Platform service
Perform the permitted operation.
Webhook
Notify the customer system of later changes.
Customer workflow
Update the application or downstream system.
DATA
Decide what system owns each piece of information.
Good integrations define a system of record, synchronisation direction, identifiers and conflict behaviour rather than copying all data everywhere.
OPERATIONS
Design for failure before launch.
- Timeouts and retry strategy.
- Duplicate webhook handling.
- Credential expiry or rotation.
- Provider outage behaviour.
- Partial workflow completion.
- Monitoring and request correlation.
NEXT
Use the technical references behind the pattern.
FAQs
INTEGRATION GUIDES FAQs
What integration pattern should I use for a custom frontend?
A secure customer backend or BFF is often appropriate when privileged credentials must remain out of the browser or mobile app.
Can I use Hamiltonn backend-to-backend only?
Yes. Supported APIs can be used for server-side integration without a Hamiltonn customer UI.
How should duplicated data be handled?
Define which system is authoritative, how identifiers map and how conflicts are resolved.
Can webhooks and APIs be used together?
Yes. APIs handle resources and actions; webhooks notify your systems of supported events.
Can enterprise customers use different integration architecture?
Yes. Dedicated Enterprise can support customer-specific integration and environment requirements.
Build on Hamiltonn Cloud.
Choose the product, modules and deployment model that fit your business, then bring the customer experience under your own brand.