DEPLOYMENT

Your work.
Your environment.

Choose who runs XRDS, where the data lives and how much your team controls. We help you make the operating decisions before the software becomes part of your day.

YOUR ENVIRONMENT / YOUR OPERATING MODEL

01 / CHOOSE THE OPERATING MODEL

Built around
your responsibilities.

Choose the environment and level of help that suit your company. Each option starts with a deployment plan and a clear support scope.

01 / WE RUN IT

Managed.

Put it to work.
Leave the operation with us.

A hosted workspace for teams that want to get started without taking on another system to operate.

Environment
Hosted by XRDS
Operation
XRDS-managed
Good fit
Teams prioritizing a supported setup

02 / MORE SEPARATION

Private.

Your own environment.
Our operating support.

A dedicated setup for businesses that need more separation and control, with help keeping it running.

Environment
Dedicated to your company
Operation
XRDS-supported
Good fit
Businesses with specific access and data boundaries

03 / YOU RUN IT

Self-hosted.

On infrastructure
your team controls.

Plan the installation and handoff with your technical team, with a clear division of maintenance and support.

Environment
Customer-controlled
Operation
Your team, with scoped support
Good fit
Organizations with an infrastructure team

FOR REGULATED WORK

Start with
the requirements.

For government contractors and organizations with stricter operating requirements, we scope the environment, access and data paths around the work. Define the required controls, who owns them and how they will be checked before deployment.

Discuss a regulated deployment

02 / MAKE THE IMPORTANT CHOICES EXPLICIT

No guessing
who handles what.

A deployment plan should answer the questions that matter once your team depends on the software.

  1. Where does the data live?

    Set the location, storage boundaries and retention requirements for your environment. Company owners can also export their company’s data from Settings.

  2. What can it connect to?

    Name the services and data paths the workflow needs. Decide what should remain inside the environment.

  3. Who can administer it?

    Define access, operating responsibilities and the process for making changes.

  4. Who keeps it running?

    Document maintenance, updates, backup and recovery responsibilities, and how your team gets help.

03 / ONE CLEAR RELATIONSHIP

One scope.
Fewer loose ends.

Bring platform access, custom work, usage and support into a clear offer. Ask us about combining those services into one AI bill.

  • Deployment and responsibility plan
  • Access and connection requirements
  • Maintenance and support scope
  • Backup and recovery arrangements
  • Operating documentation
  • A handoff with your technical team

The proposal itemizes what is included, any outside services and what your team operates. Security and regulated requirements are evaluated for the specific deployment.

See the platform that runs inside it