Userorbit self-hosting is an assisted deployment into a cloud account your organization controls. Userorbit works with your engineers on the infrastructure specification, installation and application integration, then provides administrator training and operating documentation for handover.
Use this guide to prepare for that engagement and agree the checks needed before production. The installation package, resource requirements and deployment instructions are supplied for your agreed environment.
Prepare your team and environment
Nominate an engineering owner for the deployment and an operational owner for the service after handover. Include the people who can approve cloud access, networking and the data your applications will send.
Bring the following information to the deployment discussion:
- Applications in scope. List the browser applications and environments you want to connect, including authentication flows and any embedded content. Ask Userorbit to assess native mobile or desktop applications separately before including them.
- Features and expected usage. Identify the Userorbit features you will use and provide expected active-user, event and replay volumes. These inform the infrastructure specification; there is no single resource size to assume for every installation.
- Hosting requirements. Identify the cloud account, proposed region, network restrictions and environments available for testing and production. Confirm the final architecture with Userorbit before provisioning it.
- Data requirements. Describe the data that may be collected, required retention and deletion processes, permitted processing locations and restrictions on external services. Include backups, logs and uploaded files in this review.
- Access arrangements. Agree which engineers need access, its scope and duration, and how your team will provide credentials through an approved secure channel.
Provide a staging or test environment where both teams can verify the integration with synthetic data. Do not begin with real customer records or production banking data.
Agree the deployment specification
Userorbit and your engineers should review a written specification before installation. It should identify the application components, databases, object storage and other services required by the features in scope.
The specification should also cover domains and certificates, network connections, secret management and the release being installed. Use the package and instructions supplied for that specification. A generic container command is not a substitute for this environment-specific plan.
Record where each type of data is stored and processed, including replay uploads and backups. Review external AI features, email delivery and other enabled integrations separately. Hosting the application in your cloud account does not, by itself, establish that every connected service processes data inside that account or region.
If your organization has a regional requirement, make approval of the complete data-flow and processing-location inventory a production prerequisite. Agree support responsibilities, recovery targets and any service commitments in the deployment or service schedule.
Install and connect a test application
Userorbit assists with installing the platform in the agreed environment. Your engineers provide the approved cloud and network access and participate in resolving environment-specific requirements.
Once the installation is ready for integration:
- Confirm the application endpoints, domains and certificates with the deployment team.
- Connect a test application using the SDK configuration supplied for your installation. Confirm its destination endpoints before allowing it to send data.
- Use a stable pseudonymous identifier and limit the attributes and events your application sends. Keep the mapping to real identities in your own systems.
- Configure replay privacy before testing any sensitive workflow. Begin with broad text masking and block regions that must not be recorded.
- Run representative journeys with synthetic users and inspect the resulting analytics and replays.
For the identity and replay checks, follow Protect personal data with pseudonymous IDs and replay masking.
Verify the deployment before production
Agree acceptance criteria with Userorbit and record the results in staging. At minimum, check that the features in scope work with your application, data reaches the agreed destinations, and access is limited to the intended operators.
Inspect what the SDK sends as well as what appears in reports and recordings. Check URLs, event properties and any enabled error or AI features separately from replay masking. Test sign-in, sign-out and account switching so activity is attributed to the intended pseudonymous user.
Review backup and recovery procedures with the operational owner and agree how recovery will be demonstrated. Confirm monitoring, incident escalation and the process for applying updates. If a requirement has not been verified, record it as an open item with an owner before approving production use.
Complete the handover
The handover includes administrator training and operating documentation. Review the materials with the people who will run the deployment and confirm that they can locate:
- The deployed architecture, release version and configuration inventory, with references to securely managed secrets.
- Installation, upgrade and rollback instructions for the agreed environment.
- Backup and recovery procedures, including the responsibilities and targets agreed for your deployment.
- Monitoring and incident procedures, escalation contacts and the division of responsibility between your team and Userorbit.
- The approved data-flow inventory and the retention, deletion and access arrangements.
Confirm any ongoing assistance separately from the installation engagement. Review the access granted for setup and remove temporary access that is no longer needed through your organization's normal process.
Move to production after the agreed checks pass and the operational owner accepts the handover. Keep the documentation current when the deployment, connected applications or external services change.
Arrange a self-hosting engagement
Contact your Userorbit representative with the applications, features, expected usage and hosting requirements described above. The team will confirm the supported deployment scope and the customer-specific preparation required before installation.