Skip to content
EN English
Get started

Products

AI GatewayAn OpenAI-compatible API, residency on every model
Managed kOSkOS hosted by us: Shared or Dedicated OutpostkOS inside your network, for design partners
AI BladesNVIDIA GPUs by the hour, SSH-ready

Built for

Universities Events and hackathons Regulated organisations On-premises and design partners

Company

Pricing Docs About
EN English
Colour theme
Get started Sign in

razorBridge Managed kOS · Outpost

kOS, inside your network.

A design-partner programme for connecting on-premises systems to razorBridge Managed kOS. Encrypted outbound connectivity and on-site AI are planned capabilities, to be validated with partners.

Available to design partners

Become a design partner How it connects

Design render. Outpost Blade, left, and Outpost.

Two appliances

One design, two jobs.

A design-partner programme for connecting on-premises systems to razorBridge Managed kOS. Encrypted outbound connectivity and on-site AI are planned capabilities, to be validated with partners. About Managed kOS.

The compact satin-black razorBridge Outpost with a thin teal status light. Design render

The bridge

Outpost

  • Planned: connect local systems to kOS
  • Planned: outbound-only connectivity
  • Operations to be agreed with design partners
  • Network requirements to be assessed together
The larger satin-black razorBridge Outpost Blade with front ports, a card slot and a thin teal status light. Design render

The planned bridge, plus local AI

Outpost Blade

  • Planned: the same connectivity as Outpost
  • Planned: on-site inference and embeddings
  • Cloud fallback policy to be validated with partners
  • Hardware requirements to be assessed together

How it connects

The planned connection.

Design target: an encrypted outbound-only link. Validation with design partners is still required.

Your network

Your systemsERP, mail, file shares
OutpostPlanned managed appliance
Planned: encrypted, outbound onlyDesign target: no inbound port
Your kOS workspaceSynced records would be stored here

01

Tell us about your systems

Start with the systems and records you want to connect.

02

Assess the planned connection

Review network requirements and the proposed data flow with your IT team.

03

Agree a pilot scope

Define what the pilot needs to prove before agreeing any deployment.

For your IT team

What your IT team will ask.

Something else? Talk to us.

Do we need to open inbound ports?

Outbound-only encrypted connectivity is a design target, not a deployed capability. Network requirements must be validated with each design partner.

What leaves our network?

The proposed data flow, including synced records and appliance status, will be agreed with your IT team during qualification.

Where is synced data stored?

The planned destination is your kOS workspace. Synced records would be stored there, under its hosting terms.

What does Outpost Blade keep on site?

On-site inference and embeddings are planned for Outpost Blade. Hardware, model support and offline behaviour remain to be validated with design partners.

Who operates the appliance?

Installation, updates and monitoring responsibilities will be agreed as part of the pilot scope.

How many do we need?

Appliance sizing and network coverage will be assessed with each design partner.

Get started

Become an Outpost design partner

We are qualifying design partners. Tell us which systems stay on your premises and what you need to connect.

Become a design partner Talk to us