Skip to content
MouseCat
Platform · Deployment

Deployment

MouseCat is operated by us by default, with your data scoped to your tenant. Security-sensitive customers can instead run the private cloud deployment described here: single-tenant infrastructure in your own cloud account — AWS, Azure, or GCP — jointly owned and operated by MouseCat and you.

Architecture.

customer network · no egresscloud accountisolated networkboundarycomputeyour data
MouseCat runs inside a cloud account you own, on AWS, Azure or GCP. Its data sits at the centre, encrypted with your keys, and its only outbound connections are to systems you already own — nothing reaches the edge of your network, so nothing crosses it.

What That Means in Practice.

  • Cloud-agnostic

    AWS, Azure, or GCP. Deployed as infrastructure-as-code you can read before it runs.

  • Single-tenant

    Dedicated per customer. No shared control plane. No commingling. Your data is never used to improve models for anyone else.

  • No egress

    Outbound connectivity reaches only your internal systems. No prompts or customer data go to an external model provider.

  • Your models

    Works with any gateway — Bedrock, Vertex AI, Azure, or your own internal gateway — with models called inside your boundary. Versions are pinned and approved by you. Prefer no hosted gateway at all? MouseCat runs open-weight models in your environment.

  • Scales horizontally

    Containers on your managed Kubernetes, or plain VMs with autoscaling if you'd rather not run Kubernetes.

  • Versioned

    At the image level and the code level, so a rollback is a known-good artifact.

  • Your controls

    Integrates with your existing identity provider, secret store, logging, and network policy.

Full architecture and security detail on the Security page

Get started.

We'll walk you through MouseCat live.

Book a demo