Deployment and Operations
Deployment and Operations describes how a customer, implementation partner, and DataMesh project team prepare a customer-controlled FactVerse environment for production use and keep it reliable after go-live. It covers private deployment models, container deployment, environment readiness, go-live handoff, routine operations, backup and recovery, and release maintenance.
Use this section when a project moves from product evaluation to a private customer environment, or when an existing customer-side deployment needs a clearer operating model.
Operating lifecycle
What this section covers
| Area | Main question | Read |
|---|---|---|
| Deployment model | Which environment pattern fits the customer? | Deployment Models |
| Container deployment | How is the selected customer-side model implemented? | Container Deployment |
| Environment readiness | What must be prepared before configuration starts? | Environment Readiness |
| Go-live handoff | What evidence confirms the deployment is ready for production? | Go-Live and Handover |
| Routine operations | Who checks the environment and what should be monitored? | Operations and Maintenance |
| Resilience | How are backup, restore, and recovery expectations defined? | Backup and Recovery |
| Change management | How are releases, upgrades, patches, and certificates handled? | Release and Upgrade Maintenance |
Shared responsibilities
| Responsibility | Customer | DataMesh or implementation team |
|---|---|---|
| Business scope | Define sites, products, users, data sources, and acceptance criteria. | Translate scope into deployment and configuration tasks. |
| Environment access | Provide network, domain, security, and approval information. | Confirm required access paths and configuration dependencies. |
| Identity | Provide IdP owner, users, groups, and approval rules. | Configure and validate FactVerse identity integration. |
| Data and integration | Provide source-system owners, credentials process, and test data. | Configure connectors, service identities, scopes, and validation steps. |
| Operations | Assign environment owner, support owner, and escalation path. | Provide runbook, handoff evidence, and release support. |
| Recovery | Approve backup, retention, recovery objective, and restore test expectations. | Implement or validate the agreed recovery workflow. |
When to use this section
Use these pages during the planning phase when the team needs to choose a customer-side environment pattern, confirm production responsibilities, or prepare the first deployment checklist. Use them again before go-live to make sure identity, integrations, support contacts, backup expectations, maintenance windows, and acceptance evidence are ready. After go-live, use the same section as the baseline for periodic operations reviews, release planning, recovery tests, and handover to a long-term support team.
For customer projects, the most useful output is a short operating pack. It should include the deployment model, container runtime, environment URL, tenant owner, administrator list, source-system owner list, integration inventory, support path, backup expectation, release window, and current validation evidence. The pack can be stored in the customer's own operations repository or in the governed document workspace used by the project.
Product relationships
Deployment and Operations is a shared layer. Product-specific procedures continue in their own documentation:
- use Identity and Access for sign-in, SSO, roles, and service identities;
- use Data Fusion Services for connector and dataset operations;
- use Enterprise Content Management for document governance and evidence;
- use FactVerse AI Agent for governed workflow execution;
- use product manuals for client-specific behavior in Studio, One, Importer, Designer, Inspector, and FactVerse Platform.
Read next
Start with Deployment Models for customer-side environment selection, use Container Deployment to plan the container implementation, then use Environment Readiness to prepare the implementation checklist.