An agent you can give
a real GitLab account.
Mate assumes the repository, the prompt and the agent itself can all be hostile, and is built so that none of them holds anything worth stealing.
Nothing inside the agent to leak
Your GitLab token never leaves Mate's control plane. The agent's container holds only a signed, per-job pointer, no GitLab token and no tenant identifier. The one short-lived clone token it needs is used once for git clone and then wiped.
Every action goes through a gate
The agent reaches GitLab only through a separate tool service. On each call it checks the job's permissions on the server, and tools the agent was not granted are never even offered to it. Granting is per agent, from read-only up to push, merge or close. Approving a merge request is opt-in and off by default: it never approves its own work unless you choose to.
Your model key stays in a sidecar
The model is called through a credential-proxy sidecar next to the agent. The agent container holds only a per-job placeholder; the real key is swapped in on the way out and never enters the container.
Built for code you do not trust
Repositories can be hostile. Devcontainer builds run in a Sysbox sandbox with no secrets and no access to the host Docker socket, and everything the sandbox produces is treated as attacker data. Agent containers run without privileged mode, without the Docker socket and are destroyed after each job.
Shared or dedicated workers
On Shared, tenants run on common workers: every job has its own container, but the kernel is shared. On Dedicated your workspace has a worker of its own, so no other tenant runs beside it.
Only your GitLab can start a job
Every webhook is verified against a secret you configure on the project, and forged payloads are rejected. Secrets, model keys and GitLab tokens are encrypted at rest and write-only in the console.
Payment data never reaches us
Card payments are handled by GoPay, a PCI DSS Level 1 certified payment gateway, with 3-D Secure authentication. GoPay stores the card; Mate never sees or stores card numbers and keeps only a payment reference.
EU-hosted, no tracking
The hosted service runs on EU servers. This site sets no cookies and runs no analytics. Job events and logs are kept for 30 days. If hosting is not an option, Mate runs entirely on your own servers, with nothing sent to us.
Found a vulnerability?
Email security@mate.engineer with steps to reproduce. We aim to acknowledge within a few business days and ask that you do not disclose publicly before we have had a chance to fix it. See security.txt.