Skip to content
Private beta: secure, managed business workflows for selected small teams.

Managed hosting

Keep your team focused on the work, not the infrastructure behind it.

Thorn Business Platform manages the deployment foundation around the agreed workflow, with isolated services, protected traffic, validated updates, and clear responsibilities throughout the beta.

Image: Unsplash

Managed hosting

Your business platform managed as part of the service.

Thorn manages the deployment foundation so customers do not need to assemble and operate it themselves. Each beta environment uses HTTPS, isolated application services, a private database, and validated updates.

Managed environment

DomainAgreed before provisioning
ApplicationFrontend and API
DatabasePrivate to the server
UpdatesCandidate validation and rollback

What the service removes

Focus on business workflows instead of running the platform.

Environment setup, traffic routing, deployment validation, and rollback are managed by Thorn. Beta availability, backup, recovery, and support expectations remain explicitly agreed for each trial.

1

A workspace isolated for your business

Each trial is provisioned on an agreed domain with its own application services and database rather than sharing another customer's workspace.

2

Protected public entry point

Public traffic uses HTTPS while application services and the database remain behind the server boundary, reducing unnecessary exposure.

3

Safer managed updates

Frontend and backend candidates are checked before receiving traffic, with the previous application release available for rollback if validation fails.

4

Less infrastructure burden

Thorn manages environment setup and deployment for the agreed beta workflow so the customer can focus on operating and evaluating the platform.

Operational clarity

Managed service means responsibilities are made explicit.

A trial can begin with synthetic or representative data. Any move toward important business data requires an explicit discussion of the controls and responsibilities that matter to that tester.

  • Whether real, representative, or synthetic data will be used
  • Backup frequency, retention expectations, and recovery responsibilities
  • Who can administer users, roles, and trial configuration
  • How issues are reported and what response should be expected
  • How data will be returned or removed when the trial ends

Could managed delivery remove work from your team?

Beta access is invitation-led and scoped before an environment is created.

Discuss beta access