For the complete documentation index, see llms.txt. This page is also available as Markdown.
FAQMulti-CloudCloud Platforms

Cloud Platforms

Common questions about cloud support, data residency, and infrastructure architecture in Tessell.

Platform
Topics covered

Infrastructure, certifications, Zero Data Loss, HA/DR, RBI compliance, Azure data service integrations, migration

Infrastructure, certifications, HA/DR, FSx for NetApp ONTAP


Q: Which public clouds does Tessell support?

A: Tessell is a cloud-neutral service. Database services can be hosted on:

  • AWS (Amazon Web Services)

  • Azure (Microsoft Azure)

  • GCP (Google Cloud Platform)

All four relational engines (Oracle, PostgreSQL, MySQL, SQL Server) are available on all three clouds. Regional availability details are in Supported Cloud Regions.


Q: Where are the actual database servers hosted — in Tessell's account or mine?

A: It depends on your deployment option (see Deployment Options):

Deployment option
Where database VMs and storage live

Professional, Business, Virtual Private Tessell (VPT)

Tessell's cloud account — Tessell owns and manages the underlying cloud resources

VPT @ Customer

Your own cloud account — you own the subscription; Tessell's control plane connects in to manage provisioning, patching, backups, and monitoring

VPT @ Customer is the preferred option for organisations with strict data residency or compliance requirements, because data never leaves your own cloud boundary.


Q: Why does Tessell attach multiple disks to a database server?

A: Tessell uses separate disks for:

  • Data — the primary database files

  • Logs — transaction/redo logs (separate to prevent log I/O from competing with data I/O)

  • Backups — local backup staging

This disk separation is a key reason Tessell can offer comparatively very high IOPS — each disk type is tuned independently, and I/O contention between data, log, and backup operations is eliminated.

Last updated

Was this helpful?