Mux Trust Center
Your code. Your workspace. Clear controls.
Mux gives your team a shared code index and cloud sandboxes. This is where we explain how access works, where data goes and who helps us run the service.
About this center
Mux maintains these descriptions from its implementation. Cloudflare provides the cloud infrastructure; its Trust Hub covers Cloudflare's policies and certifications.
Security controls
Access checks and isolation built into the service.
Private workspaces
API requests check the caller's membership and workspace access before returning private workspace data.
Scoped keys
Workspace keys belong to a member and carry a role. You can revoke keys and signed-in devices from the product.
Repository selection
You choose which repositories to index, within the access your GitHub installation grants.
Isolated cloud tasks
Each cloud task has its own Linux container on Cloudflare. Only the member who starts a task can read or control its thread.
Credentials outside the container
A gateway adds the credentials needed for approved outbound requests. The task container does not store those credentials.
Encrypted transport
The public website and APIs use HTTPS. The service processes the content it needs to run your index and cloud tasks.
Your data and AI
What the service needs, and what you control.
- Code and index
- Mux mirrors and indexes the repositories you select. Workspace members and keys need access to query that index.
- Agent tasks
- A local task runs on your Mac. A cloud task runs on Mux and sends the prompts and context needed for that task to the model provider you choose.
- Repository removal
- Deselecting a repository removes its mirror and its part of the index. Our data policy explains retention, account closure and data requests.
Service providers
The services involved depend on the features and accounts you use.
- Cloudflare
- Application hosting, databases, object storage, code indexing, cloud containers and the model gateway.
- GitHub
- Connected repositories, repository permissions and optional account sign-in.
- Polar
- Checkout, subscriptions, payment processing and merchant-of-record services. Mux does not store full payment-card numbers.
- Your model provider
- The prompts and context needed for the task you run. The provider and its data terms depend on the model and account you choose.
- Your sign-in provider
- Account authentication when you choose a supported social sign-in option.
Resources
Policies, product documentation and infrastructure information.
Customer reviews
Read customer feedback on Trustpilot, or share your experience with Mux and muxcode.
Common questions
Where does Mux run?
Mux runs its cloud service on Cloudflare Workers, Durable Objects, D1, R2, Artifacts and Containers. A local muxcode task runs on your Mac; a cloud task runs on Mux.
Does Mux use my code to train models?
Mux does not use your code to train models, sell personal data or use private workspace content for advertising. Your selected model provider processes the prompts and context you send under the terms of your account with that provider.
Can I control which repositories Mux reads?
Yes. The GitHub installation limits repository access, and your workspace selects which repositories to index. You can deselect a repository, revoke a workspace key or disconnect GitHub.
Does Mux publish a SOC 2 report or ISO 27001 certificate?
This center describes Mux's own technical controls. Mux does not publish a SOC 2 report or ISO 27001 certificate here. Cloudflare's certifications cover Cloudflare's services and do not certify Mux.
How do I request security information?
Email hello@usemux.com with your question or the documents you need. Use the same address to report a suspected security issue or request help with your data.