Skip to content

Deployment & rollout

Live in your own environment in under five days

It's a standalone architecture: one unit that installs into an environment you already control. We set it up and run it for you, and nobody on your side needs to learn anything new.

Talk through your setup Security & compliance

Four places it can run, all of them under your control.

Your AWS account

Your VPC, your keys, and the model on AWS Bedrock in your own account and region.

Your Azure subscription

Inside your tenant, under the network policy you already enforce.

Your Google Cloud project

The same controls you apply to everything else you run.

Your own servers

Fully on-premise, with models served by Ollama or any other self-hosted runtime, so nothing needs to leave the site. We configure it with you during deployment; the platform has run fully self-hosted before.

Day one to team-wide, without a migration.

Three steps. Your existing systems keep running exactly as they do today throughout all of them.

From signature to first answer

Three steps, and the first one takes under five days.

  1. 01

    Deploy

    Live in your own infrastructure in under 5 days. We handle the install and keep running it.

    • · Environment and network agreed up front
    • · Single sign-on wired to your identity provider
    • · Second-factor policy set per group
  2. 02

    Connect

    Start with your documents; add Drive, email, Microsoft, databases or CRM/ERP as scoped integrations.

    • · Standard connectors switched on first
    • · Custom connectors specified before any work starts
    • · Read-only by default
  3. 03

    Roll out

    Define groups and passage-level rules, then open it up team by team.

    • · Bulk tagging on the existing library
    • · Token budgets set per person and team
    • · One department at a time, at your pace

Licence & ownership

You own the install. Not a seat in ours.

The platform is delivered under a perpetual licence, with the source code delivered. It is not a subscription to a service we operate, and it does not stop working if a commercial relationship ends.

That matters because vendor terms move. Through 2025 and 2026, leading AI vendors shifted consumer training to opt-out, and the most capable frontier models began carrying mandatory 30-day retention on every platform, cloud marketplaces included. None of that reaches an install you own and run.

Exactly what reaches the model

Perpetual licence

The right to run it does not expire with a billing cycle.

Source code delivered

Your security team can read what is running in your environment.

No terms update can change it

Your compliance posture is set by your configuration, not by our roadmap.

Run and supported by us

Owning the install does not mean operating it alone. Our team sets it up and keeps it running.

What we need from your side.

Four things, and none of them involve a migration. Your current systems keep running exactly as they do today.

  • An environment

    A cloud account or servers, and someone who can approve what gets provisioned in it.

  • A first document set

    The library one team already depends on. It does not need cleaning up first.

  • Your group structure

    Who belongs to which team, and which of them should not see what.

  • An identity provider

    Whatever you already use for single sign-on. No second directory to maintain.

Bring your infrastructure team to the demo

Book a demo

30-minute demo, on your files, no commitment.