Get started

    Deploy your
    first confidential app.

    Two paths in — managed or self-hosted. Pick the one that matches how much of the infra you want to run yourself.

    Path 01

    Deploy your first app

    Request access to the hosted platform. Push a container, get a confidential application running on a TLS endpoint. The fastest way to see what Enclava actually does.

    • Invite-only early access
    • CPU containers on AMD SEV-SNP — bring any OCI image
    • TLS, custom domains, encrypted volumes included
    • Public attestation per deploy

    Capacity is limited. Request access and we'll get back to you.

    Path 02

    Run the engine yourself

    The deploy engine is open source. If you operate your own SEV-SNP-capable hardware (or you want to white-label), self-host the platform and skip our managed cloud entirely.

    • Open source, MIT-licensed engine
    • Runs on your own AMD SEV-SNP clusters
    • Brand it / resell it as your own product
    • Documentation + community support

    Best when you already operate Kubernetes and SEV-SNP hardware.

    What happens next

    If you choose path 01.

    1. 01We get back to you with access and a quickstart link.
    2. 02You install the CLI and run enclava deploy with any container.
    3. 03Your app boots inside a TEE with TLS and a public URL.
    4. 04You verify the attestation, share it with your team, ship.