Skip to main content

Now accepting design partners.

Request a demo

Deployment

The same platform in every boundary.

Run REAEGIS in our cloud, inside your authorization boundary, or in an enclave with the network cable cut.

REAEGIS cloudIn your boundaryAir-gapped

outside

no outside link needed

authorization boundary

TrivyGrype

scanners

findings

REAEGIS

pull requestsGitHub

repository

Runs in
Your IL4 or IL5 environment
Crosses the boundary
Nothing
Sign-in
CAC and PIV through your identity provider

Start from what your boundary allows.

Two questions settle it. The same engines run wherever you land.

If findings and pull requests can cross your boundary, choose REAEGIS cloud. If not, and there is a network path out, choose In your boundary. If the network cable is cut, choose Air-gapped.

START WITH YOUR BOUNDARY

  1. QUESTION 01

    Can findings and pull requests cross your boundary?

    YES

    REAEGIS cloud

    All plans

    Hosted by REAEGIS. Findings and pull requests cross the boundary.

  2. QUESTION 02

    Is there any network path out?

    YES

    In your boundary

    Enterprise

    Runs inside your IL4 or IL5 boundary. Nothing crosses.

  3. NO PATH OUT

    The network cable is cut.

    Leads to

    Air-gapped

    Enterprise

    Runs inside your enclave. A signed kit comes in, inbound only.

Three models, compared line by line.

The engines stay the same. Where they run, and what crosses the boundary, is the difference.

REAEGIS cloud

OUTSIDE YOUR BOUNDARY

BOUNDARY

Where it runs

REAEGIS cloud, outside your boundary

What crosses the boundary
Crosses:

Findings and pull requests

ACCESS

Sign-in

SAML 2.0 and OpenID Connect

DATA AND EVIDENCE

Vulnerability data

Live vulnerability feeds

Transparency log

Public Sigstore Rekor log

eMASS

Export files

Your ISSO imports them

OPERATIONS

Remediation

Pull request, a person approves

Updates

Managed by REAEGIS

Plan
All plans

In your boundary

INSIDE IL4 OR IL5

BOUNDARY

Where it runs

Inside your IL4 or IL5 boundary

What crosses the boundary
Does not cross:

Nothing

ACCESS

Sign-in

CAC and PIV through your identity provider

DATA AND EVIDENCE

Vulnerability data

Inside the boundary

Feed delivery agreed during scoping

Transparency log

Agreed during scoping

eMASS

In-boundary agent

Uses a PKI credential you own

OPERATIONS

Remediation

Pull request, a person approves

Updates

On your schedule

Plan
Enterprise

Air-gapped

INSIDE AN ENCLAVE

BOUNDARY

Where it runs

Inside your enclave

What crosses the boundary
Crosses:

A signed update kit, inbound only

ACCESS

Sign-in

CAC and PIV through your identity provider

DATA AND EVIDENCE

Vulnerability data

Offline database

Updated by scheduled transfer

Transparency log

Internal transparency log

eMASS

Agreed during scoping

OPERATIONS

Remediation

Pull request, a person approves

A deterministic rule engine covers about 80% of findings with no external service

Updates

Signed kit

Verified with Cosign before install

Plan
Enterprise

Same engines in every model

  • RAMPART
  • ADVERSARIUS
  • AXIOM
  • PHAROS
  • CHRONICLE
  • ARE

Exactly what crosses the boundary.

Flows are drawn in blue. Where no blue line crosses the boundary, nothing crosses.

01

REAEGIS cloud

2 flows cross

REAEGIS cloud runs outside your boundary. Pull requests flow in to your repository, and findings from your scanners flow out to REAEGIS cloud.
INTO YOUR BOUNDARY
Pull requests
OUT OF YOUR BOUNDARY
Findings

02

In your boundary

0 flows cross

REAEGIS runs inside your boundary with your repository and scanners. No link to the outside is needed, so nothing crosses.
INTO YOUR BOUNDARY
Nothing
OUT OF YOUR BOUNDARY
Nothing

03

Air-gapped

1 flow, inbound only

REAEGIS runs inside your enclave. The outside link is cut. A signed update kit comes in, and your ISSM verifies it at the enclave wall. Nothing goes out.
INTO YOUR BOUNDARY
Signed update kit
OUT OF YOUR BOUNDARY
Nothing
  • Flow
  • Authorization boundary
  • Enclave wall, no network path
  • Cut link
How the platform is secured

What arrives in the kit.

One signed, versioned bundle. Your ISSM verifies it before anything is installed.

KIT CONTENTS

Signed update kit

ROUGHLY 8 TO 12 GB

  • Signed with Cosign
  • Versioned
  • Scanner engines

    The scanners run inside the enclave

  • Offline vulnerability database

    Updated by scheduled transfer

  • Internal transparency log

    Evidence is anchored inside the enclave

  • Deterministic rule engine

    Covers about 80% of findings with no external service

INSTALL, IN FOUR STEPS

  1. 1

    ISSM verifies the signature

    Cosign checks the bundle against its signature before anything is installed.

    $ cosign verify-blob reaegis-kit.tarVerified OK
    ISSM
  2. 2

    Transfer through your approved process

    The kit moves by your ISSM-approved transfer path.

  3. 3

    Install inside the enclave

    Everything in the kit runs inside the enclave.

  4. 4

    Vulnerability data refreshed on schedule

    The offline database is updated by scheduled transfer.

Inbound only. Air-gapped deployment comes with the Enterprise plan.

REAEGIS for DoD programs

Your identity provider stays in charge.

People sign in the way they already do, through the identity provider you run.

SIGN-IN

SAML 2.0 or OpenID Connect

REAEGIS cloud

The user signs in through your identity provider, which uses SAML 2.0 or OpenID Connect to sign them in to REAEGIS cloud.

SIGN-IN

CAC and PIV

In your boundaryAir-gapped

Inside your boundary or enclave, the user presents a CAC or PIV card to your identity provider, which signs them in to REAEGIS.

Federal programs are invitation only. Commercial teams self-register with single sign-on.

In-boundary and air-gapped start with a scoping conversation.

  1. 1Scoping conversation

    Your boundary, your frameworks and your transfer process.

  2. 2Kit or install plan

    An install plan for your boundary, or a signed kit for your enclave.

  3. 3First system connected

    A first repository and its scanners, connected inside your boundary.

Enterprise plan

In-boundary and air-gapped come with the Enterprise plan.

See pricing

Authorization is not a destination. It is a system property.

Request a demo and we will walk one finding from detection to signed evidence.

  • Federal programs

    Invitation only, with CAC and PIV.

    Request access
  • Commercial teams

    Self-register with single sign-on.

    Create a workspace
  • Pricing

    Plans start at $2,500 per month. In-boundary and air-gapped deployments are scoped per program.

    See pricing