Customer-hosted deployment
Run XSheet on your own infrastructure.
Run the application, model publishing and calculation APIs in your own environment. Your team controls access, model releases and the data you retain. Workbooks and calculation inputs do not need to be sent to XSheet to publish or run a model.
Inside your environment
The complete platform runs alongside your applications.
Your team operates model administration and the calculation service together. There is no vendor-hosted calculation or model-management service in this path.
Your infrastructure
Customer-hosted XSheet
Your model team
Maintains the workbook in Excel
XSheet application
Versioning, verification and release approvals
Isolated build
Prepares the workbook as a calculation service
Your applications
Quoting, policy and banking systems
XSheet API
Authenticates callers and selects the model version
Isolated calculation
Runs the model without Excel
Stored within your installation
Workbook versions and their builds · configuration · audit records and retained call history
Connections to review separately
Configured identity provider · signed software delivery · monitoring, notifications and backup destinations
Review internet and offline requirementsOne installation
Keep the model lifecycle under your control.
-
Application and administration
Model authors, approvers and auditors use the application for their own roles. Environments carry separate policies, and protected environments change through approved promotions.
-
Publishing and calculation
Workbooks become services within the installation. Calculations run isolated from the API and from workbook processing. Excel is not needed at calculation time.
-
Workbooks and records
Workbook versions and their builds, configuration and call history belong to the installation. Retention and payload policies determine which call data is kept.
-
Access and integration
People join by invitation and use configured enterprise sign-in or local accounts with an authenticator. Applications use scoped API keys for the environment and services they need.
Internet and offline operation
Calculations run locally. Other connections need their own review.
The calculation path does not require a connection to an XSheet-operated service. A requirement for no external communication across the entire installation also covers sign-in, software delivery and operational tools. Fully air-gapped deployment has not yet been validated.
-
Day-to-day API calls
Your applications reach the API on your network. The installation checks their API keys, runs the model and records the result locally. That path does not send the workbook or request to a vendor service.
-
People signing in
Local accounts use a password and authenticator code. Configured enterprise SSO needs access to its identity provider, including discovery and sign-in endpoints. An internet-dependent provider remains an internet dependency.
-
Installation and updates
Software delivery is separate from calculation traffic. The existing update process downloads and verifies signed releases using external release, registry and trust services. An offline installation and update procedure requires separate validation.
-
Operations and support
Monitoring, notifications and backup destinations can create additional connections. Document them, along with DNS, time synchronization and certificate renewal. Agree support access and what diagnostic information may be shared.
Who operates what
Your team operates the environment. XSheet supplies the software.
Use this division of responsibilities to start the deployment review. Confirm the final operating model, support scope and access arrangements in your agreement before production use.
| Area | Your team | XSheet |
|---|---|---|
| Infrastructure and network | Operate the infrastructure, network, TLS and permitted connections. | Define software requirements and document the component boundaries. |
| Models and production releases | Own the workbook, expected results and approval of model changes. | Provide model publishing, verification and governed release controls. |
| Identity and permissions | Manage accounts, roles, API keys and any identity-provider configuration. | Provide authentication, authorization and audit controls. |
| Secrets and keys | Control secret storage, access and rotation; review any required KMS integration. | Document the software’s key and secret requirements. |
| Data and recovery | Set retention and residency requirements, own RPO/RTO targets, maintain backups and test restoration. | Provide data-handling controls and documented recovery procedures. |
| Software updates | Plan maintenance, validate changes and operate the installation’s update process. | Supply signed releases and release information. |
| Logs and incidents | Control log access, retention and export to your monitoring or SIEM tools; run your operational response. | Provide diagnostics and product support within the agreed scope. |
| Software security | Assess releases and apply agreed security updates. | Maintain the software’s security controls, dependencies and release integrity; agree vulnerability remediation and advisory procedures. |
| Support access | Approve any access and the diagnostic information shared. | Agree the access method, scope and handling of support data with your team. |
Deployment review
Define the operating requirements before production.
-
Location and access
Choose the installation location against your data-residency and contractual requirements. Review TLS termination, permitted callers, administrator access and the configured identity provider.
-
Release delivery
The updater verifies signed artifacts against pinned trust before installation. Agree how releases reach your environment, how updates are validated and what connectivity the verification process needs.
-
Operations and recovery
Document responsibility for keys, backups, restore drills, monitoring and incident response. Review the recovery procedure alongside the retention rules and legal holds that apply to your data.
-
Capacity for your models
Size the installation using representative workbooks and traffic. Measure the complete request path, resource consumption and failure behavior before setting operational targets.
Deployment questions
What the deployment model means for your team.
- Can XSheet run in our environment without communicating with your company?
- Model administration, publishing and API evaluation run in your installation; the calculation path does not call an XSheet-operated service. A guarantee of no external communication for the whole installation needs a separately validated configuration and software-delivery process. Fully air-gapped operation is not yet a validated deployment option.
- What happens if xsheet.io is unavailable?
- A customer-hosted installation serves calculations on its own API hostname. Its model administration, publishing and evaluation do not depend on the public xsheet.io website. An outage does not by itself stop those local operations. Configured identity, software-delivery and operational services have their own availability requirements.
- Is the calculation runtime the only part we operate?
- The customer-hosted model covers the application, administration, workbook publishing, calculations and persistent data. It is a complete installation, with the same versioning and promotion workflow.
- Does XSheet need access to our production data for support?
- Support access and diagnostic sharing must be agreed with your team. Operating the software on your infrastructure does not itself grant XSheet access. Define what may be shared, by whom and for which support activities.
- Can an installation be arranged for a required region?
- The product design also allows regional installations. Location, operating responsibilities and contract requirements must be agreed before client production data is introduced.
- Does deployment establish regulatory compliance?
- Deployment location and technical controls are parts of a wider assessment. Contracts, operating procedures and the evidence your security and compliance teams require must be reviewed separately.
Start with the workload
Review your model and its operating environment.
Bring the workbook requirements, expected traffic, identity setup and data-handling constraints to the evaluation. If your network must be disconnected, make that an explicit acceptance requirement for installation, routine operation, updates and recovery.
XSheet
See how your model would work as an API.
Discuss the workbook your team maintains and the applications that need its results. Explore integration and deployment in your environment.