This article explains where your Tascus data lives, who manages it, and who can access it. It covers the three supported hosting models so you can choose the one that fits your security, IP, and IT requirements.
Your data is yours
Whichever hosting model you choose, the principles are the same:
Standard SQL Server. All production data — work instructions, process configuration, results, and traceability records — is stored in a standard Microsoft SQL Server database. There is nothing proprietary in the data layer.
Media files (images and video) are held in standard file storage (Windows file server, SharePoint, or Amazon S3). Neither uses a proprietary format.
No lock-in. Because it's a standard SQL connection, you can query, back up, or export your data at any time, including pulling it into your own data lake or reporting tools.
You decide where it lives. The hosting model determines who holds and manages the data. You are not required to place your data in any environment you don't control.
Tascus is a .NET application that handles the web services, data layer, and (where applicable) cloud hosting. The shop-floor operator client uses a LabVIEW runtime for reliable hardware integration and barcode scanning. Only the database stores your production data, and that database is always standard SQL Server.
The three hosting options
On-premises | Azure Client Owned | Azure Metis-managed | |
|---|---|---|---|
Where data lives | Your own servers / network | Your Azure subscription | Metis Automation's Azure account |
Media files jpg / png / mp4 | Windows sever | SharePoint or Amazon S3 | Amazon S3 |
Infrastructure managed by | You | You | Metis |
Backups & disaster recovery | You | You | Metis |
Region / residency control | Full | Full (you choose region) | Each customer's data is stored in its own isolated database, encrypted in transit and at rest. |
Metis access to your data | None unless you grant it | None unless you grant it | Access is restricted to authorised Metis personnel for support and maintenance only, under controlled and logged conditions. |
Customer setup effort | Highest | Medium | Lowest |
Best for | Maximum IP control, restricted or air-gapped sites | Cloud convenience under your own governance | Fastest start, minimal IT overhead |
On-premises
Tascus runs entirely on your own infrastructure. The SQL Server database and the .NET services sit inside your network.
Data location: Your servers only. Data never leaves your network.
Who manages it: Your IT team handles the servers, security, backups, and disaster recovery.
Metis access: None. Metis has no route to your data unless you explicitly provide remote access for support.
Choose this if: Your IP requirements demand that production data stays fully inside your perimeter, or you operate restricted / air-gapped manufacturing environments.
Your own Azure
Tascus is deployed into your organisation's own Azure subscription. You get the convenience of cloud hosting while keeping the data under your own cloud governance.
Data location: Your Azure tenancy, in a region you choose.
Who manages it: You own the subscription, access control, and billing. Metis can assist with deployment and support.
Metis access: None by default. Any support access is under your control and policies.
Choose this if: You want cloud scalability and remote access, but require data to remain within your own cloud governance and region.
Metis-managed Azure
Tascus is hosted in Metis Automation's Azure account, with Metis managing the underlying infrastructure, updates, and backups.
Data location: Metis Automation's Azure environment, hosted in your choice of UK or USA region.
Who manages it: Metis manages infrastructure, patching, and backups, reducing the load on your IT team.
Isolation: Separate database per customer
Metis access: Metis technical team for support only.
Backups: Automated backups with point-in-time restore are retained for 35 days, stored on geo-redundant storage within your agreed region.
Recovery point objective (RPO): no more than 1 hour of data.
Recovery time objective (RTO): service restored within 1 business day of a confirmed restore request.
Media files (images, video) stored in SharePoint or Amazon S3 with native redundancy and versioning, and included in the data export on exit.
Data on exit: Full SQL export provided, data deleted within 30 days.
Choose this if: You want the fastest start with minimal IT overhead and are comfortable with your data residing in a Metis-managed environment.
Choosing the right option
Choose On-premises if maximum IP control and keeping data inside your own perimeter is the priority.
Choose Your own Azure if you want cloud benefits but need data under your own governance and region.
Choose Metis-managed Azure if you want the simplest setup and least IT overhead.
You can also start on one model and migrate later — because the data is standard SQL Server, moving between environments is a database migration, not a re-platforming exercise.
Related articles
System Requirements
Installation
Windows Server Installation
Database Setup & Maintenance
Licensing
