Dedicated Enterprise
Dedicated where isolation matters.
For organisations that require greater separation than a standard platform environment, Hamiltonn can provide dedicated deployment architecture around the selected product and operating model — while Hamiltonn continues to maintain the software platform underneath.
What is a dedicated SaaS deployment?
Separate the customer environment. Keep the platform maintained.
A dedicated SaaS deployment provides a customer with separately allocated technical resources or environments rather than relying entirely on shared application infrastructure.
With Hamiltonn Cloud, dedicated architecture can include customer-specific application runtime, database, storage, credentials and environment configuration while Hamiltonn continues to maintain the underlying software platform.
Clear ownership
Dedicated infrastructure. Hamiltonn technology.
Dedicated deployment changes the infrastructure architecture; it does not automatically transfer Hamiltonn source code or intellectual property. The customer receives the agreed service and customer-specific environment while Hamiltonn retains and maintains the reusable platform technology.
Who it is for
For organisations with requirements beyond standard SaaS.
Enterprise
Complex procurement, security, integration or operational requirements.
Fintech & digital assets
Eligible workloads where greater customer-specific environment separation is preferred.
Software companies
Dedicated backend infrastructure behind a custom customer-facing product.
Large partners & resellers
Customer ecosystems that need a dedicated platform operating boundary.
Why dedicated
Answers for enterprise procurement.
Data isolation
Customer-specific application, database and storage boundaries within the agreed dedicated architecture.
Enterprise controls
Access policies and configuration aligned to your governance.
Deployment flexibility
Environment configuration shaped around your requirements.
Controlled releases
Updates on a schedule that fits your change management.
Auditability
Logs, access records and documentation available for review.
Enterprise support
Named contacts and defined response expectations.
Specific isolation boundaries, data residency options and support terms are agreed per engagement — we would rather scope precisely than promise loosely.
Isolation layers
Dedicated architecture can separate the parts that matter.
The exact dedicated boundary is designed around the customer and product. Not every deployment needs every dedicated component.
Application environment
A customer-specific application runtime and configuration boundary.
Database
A database allocated to the customer environment where required.
Storage
Customer-specific boundaries for supported files, documents and application data.
Credentials & configuration
Secrets and environment settings scoped to the dedicated deployment.
Dedicated does not necessarily mean exclusive physical hardware. The service defines the customer-specific technical and operational boundaries.
Combine deployment models
Dedicated can still be managed, headless and white-labelled.
Dedicated + Managed
Hamiltonn continues to operate the dedicated application environment for your organisation.
Dedicated + Headless
Your frontend connects to a customer-specific Hamiltonn backend environment.
Dedicated + White Label
Customer-specific infrastructure can still present your organisation as the customer-facing brand.
Environments & releases
Greater release control without permanent software divergence.
Dedicated Enterprise can support separate development, staging/UAT and production environments with coordinated release windows and customer acceptance processes. The product remains part of the maintained Hamiltonn software line rather than becoming an uncontrolled fork.
Development
Implementation, configuration and integration work.
Staging / UAT
Customer review, validation and acceptance testing.
Release checks
Automated tests, migrations and operational readiness.
Production
Controlled promotion into the live customer environment.
Health verification
Confirm the deployment and core services after release.
Ongoing maintenance
Hamiltonn continues to maintain the underlying product.
Operations
A dedicated environment needs a defined operating model.
Monitoring & observability
Customer-specific health, logs, metrics and operational context for agreed platform components.
Backups & recovery
Defined backup, restoration and recovery processes around the dedicated environment.
Incident management
Distinguish platform-wide incidents, dedicated customer incidents and third-party provider failures.
Security & data
Reduce unnecessary shared boundaries.
Dedicated architecture can support customer-specific access, credential, network, database and storage boundaries alongside the application security controls of the Hamiltonn platform.
Regional deployment, data-residency, customer-specific keying or private connectivity can be evaluated as enterprise architecture requirements when relevant to the selected service.
- Identity and privileged-access controls
- Customer-specific secrets and configuration
- Network and integration boundaries
- Auditability and controlled change
Enterprise integration
Connect the dedicated environment to your existing architecture.
Dedicated deployments can integrate with customer identity, CRM, ERP, financial providers, digital-asset infrastructure, communications, analytics and other enterprise systems through supported interfaces.
Dedicated API
Use supported Hamiltonn APIs against the customer-specific environment.
Enterprise identity
Connect staff authentication to supported customer identity architecture where required.
Private connectivity options
Evaluate network restrictions or private connectivity patterns as part of enterprise solution design.
Implementation
Dedicated deployment starts with architecture, not a checkout button.
We define product, data, integrations, environments, security boundaries, release expectations and operational responsibilities before provisioning the enterprise environment.
Discovery
Product, scale, data, region and integration requirements.
Architecture
Application topology, data boundaries, networking and environments.
Responsibility matrix
Define Hamiltonn, customer and third-party responsibilities.
Provision & integrate
Create environments and connect required systems.
Test & review
Functional, integration, security and acceptance validation.
Launch & operate
Production deployment and ongoing enterprise operation.
Commercial model
Dedicated infrastructure has an enterprise service model.
Pricing is determined around the selected product, platform licence, infrastructure, database, storage, environments, usage, integrations, implementation and support requirements.
Dedicated ≠ self-hosted
Hamiltonn can host and operate the dedicated environment. Customer-hosted, on-premise or deployment into a customer-owned cloud account would be a separate architecture model if offered.
Frequently asked questions
Who maintains the software in a dedicated deployment?
Hamiltonn does. You get infrastructure isolation and release control; the platform itself is still built, updated and supported by us.
Can dedicated deployments use the API?
Yes — the full API surface is available against your dedicated environment.
Is dedicated only for very large companies?
It is for any organisation whose risk, data or procurement requirements call for isolation — size is not the test.
Does dedicated mean I own the Hamiltonn source code?
No. Dedicated deployment changes the infrastructure boundary, not ownership of Hamiltonn's underlying platform technology.
Does dedicated mean I get exclusive physical hardware?
Not necessarily. Dedicated Enterprise provides customer-specific environment boundaries; underlying infrastructure services can still use shared cloud control planes where appropriate.
Can Hamiltonn still manage a dedicated deployment?
Yes. Dedicated architecture and managed operations are complementary. Hamiltonn can operate and maintain the dedicated customer environment.
Can I use my own frontend with Dedicated Enterprise?
Yes. Dedicated Enterprise can be combined with the Headless/API model so your applications connect to a customer-specific Hamiltonn backend.
Can we require staging before production?
Dedicated architecture can include staging or UAT and coordinated release gates as part of the agreed enterprise environment model.
Is Dedicated Enterprise the same as on-premise or customer-hosted software?
No. The standard dedicated model can remain hosted and operated by Hamiltonn. On-premise or customer-cloud deployment would require a separate architecture and service agreement.
Scope a dedicated deployment.
Bring your requirements — isolation, residency, release control — and we will map them to an environment design.