Security at superglue.

superglue connects to your clients' ERPs and databases. Client credentials stay encrypted, private systems stay behind their firewall, and nothing is written without approval. The Trust Center has our reports and policies.

SOC 2 Type 2ISO 27001 in progressAES-256 encrypted credentialsNo training on client data
Compliance

Reports and policies in the Trust Center.

The Trust Center has our SOC 2 report, our policies and our subprocessors. Security questions go to security@superglue.ai.

SOC 2 Type 2

superglue holds a SOC 2 Type 2 report. Request it in the Trust Center.

ISO 27001

The ISO 27001 certification of superglue is in progress.

Data Processing Addendum

superglue acts as a processor for the client data you work with. A Data Processing Addendum covers that processing.

Subprocessors

The subprocessors are listed in the Trust Center and in the privacy policy.

Self-hosting

Run superglue on your own infrastructure.

You can run the full superglue platform in your own cloud or data center. Your data, brain and playbooks are stored there, and our team deploys the instance and installs updates. The agents use the superglue model, which is trained for implementation work and served through our model gateway.

Stored in your environment

Data

Client records that a migration moves, and the mappings and reconciliations built from them.

Brain

Your meeting notes, workspace documents and email, indexed in your environment.

Playbooks

Your standards, migration patterns and quality checks, stored with the rest of your data.

Credentials

System credentials are stored in your environment, encrypted with a master key you own.

Model calls go to the superglue model on AWS Bedrock, which processes them in memory and stores nothing. There is no license check, and telemetry is off by default.

Deployment

We do the deployment.

You grant access and delegate a subdomain. We deploy and configure the instance and hand it over to you.

  1. 1

    You grant scoped access

    We create IAM roles with a superglue prefix. These roles can only change the resources we create.

  2. 2

    You delegate a subdomain

    For example superglue.yourcompany.com, pointed at the instance in your account.

  3. 3

    We deploy and configure

    We set up the runtime, storage, the superglue model and SSO with your identity provider. If you have on-prem systems, we also set up the Secure Gateway.

  4. 4

    You get a running instance

    Your instance has the same features as our cloud. We install updates from then on.

Where and how it runs

  • AWS, Azure, GCP or your own hardware
  • Single-tenant deployment
  • Region of your choosing, including EU-only
  • Docker or Kubernetes
  • Secure Gateway for systems that are not on the public internet
Updates

We keep your instance up to date.

We publish new versions of superglue and install them on your instance on a schedule you approve.

Upgrades by our team

Our team runs every upgrade. You decide when it happens.

Rollback

Every release is a versioned image. If a release causes a problem, we roll back to the previous version.

Monitored and supported

Monitoring and support are included.

Cloud or self-hosted

Our cloud and your cloud.

superglue has the same features in our cloud and in your own environment.

FeatureOur cloudYour cloud or on-prem
Agents, Brain, Playbooks, Capabilities
Any API, database or legacy system
Scheduling & webhook triggers
Access rules (RBAC) & SSO
Run monitoring & Activity Tracker
Secure Gateway to on-prem systems
Data and brain stored in your environment–
Deployment & updates by superglueOn your schedule

Clear your client's security review.

Send the Trust Center to the client's IT team, or talk to us about a proof of concept deployed the way their security team requires.