Deployment model

ServiceMatch deploys single-tenant, in the environment where the engagement lives — your cloud or your customer's. There is no SwipeLeft-hosted multi-tenant service, by design: discovery data describes an organization's entire estate, and it should never leave that organization's control.

The shape of an install

• →A self-contained Docker Compose stack: frontend, API, pipeline engine, and database, fronted by its own reverse proxy.
• →Images-only distribution — no source checkout required to run it.
• →One disclosed runtime dependency: the AI authoring layer calls api.anthropic.com on your own key. Image pulls reach the container registry at install and update time; everything else runs local to the stack. AI features degrade gracefully when the key is absent — the pipeline runs without them.
• →Teardown is one command plus deleting the directory.

Boundaries we hold

• →Discovery data never leaves the deployment environment; exports and their provenance manifests are the only products.
• →The operator console gates destructive actions on explicit confirmation, runs against a pinned capability set, and enforces per-session spend caps on the AI layer.
• →Nothing phones home: no vendor telemetry from customer deployments.