Invite codes no longer gate your own accounts. Bring-your-own-account use is free for everyone; cloud Pro stays invite-only.Read the announcement
AnnouncementAugust 9, 2026

To everyone who's been following or using Mirasim:

Over the past few days, Mirasim ended up in front of a much bigger audience much earlier than we'd planned. We were still in private beta and, honestly, nowhere near ready for a wider launch.

Invite codes spread far beyond the small beta group we had planned for. In a very short window, we saw a flood of visits and test requests, along with some unusually aggressive, probing request patterns. Our capacity, reliability, and security systems weren't ready for that volume. Some of you ran into slow loading, failed requests, or Pro benefits that never showed up.

We're genuinely sorry for the rough experience. Whatever the source of the traffic, we should have been better prepared. That's on us, and our users shouldn't have to pay for it.

At the same time, you sent us a huge amount of honest, detailed feedback. A lot of issues that probably wouldn't have surfaced until a public launch showed up early. Thank you to everyone who took the time to try Mirasim, patiently share feedback, or report security issues responsibly.

Here's how access to Mirasim will work from here

Invite codes no longer limit connecting your own accounts to Mirasim — they only limit the cloud Pro service that Mirasim pays for.

Connecting and using your own accounts locally will be free for everyone. You'll be able to connect the Claude Code, Codex, and other model accounts or services you already use, then work across multiple models, Agents, and sessions in Mirasim. Mirasim won't charge for any of this. Third-party subscription or API fees will still follow each provider's own terms.

Cloud Pro access — where Mirasim covers the model usage costs to make things cheaper for users — will remain invite-only and roll out in batches as capacity allows. We'll keep sharing our progress and what opens next, so the rules stay as clear and transparent as possible.

A note on Pro benefits

  • The 1,000 beta users covered by our original promise will still receive one full year of Mirasim Pro. That promise has not changed.
  • Anyone who successfully registered during this wave after we had already passed the original 1,000-user limit will receive one month of Mirasim Pro. This is both to make up for the unstable experience and to thank you for trying Mirasim before it was fully ready.
  • If you've already registered or activated your access but your Pro benefits still aren't showing up, please don't try again. We have the records. We'll verify eligibility and apply the benefits in batches, then share the timing and start-date details.

How the rollout will work from here

Over the next week or two, we'll focus on adding capacity, fixing the entitlement system, tightening security, and working through your feedback one issue at a time. Mirasim remains open. Registration and local, bring-your-own-account access will stay available, while cloud Pro access will roll out in batches as capacity allows.

We're not trying to build yet another model aggregator. We want Mirasim to be an Agent workspace you can keep building in for the long run. Wherever the next leap in Agent capability comes from, you should be able to plug it into the same workflow, switch seamlessly, and use different Agents together. Once you've built something, you can put it in front of simulated users in a real environment and let evidence — not guesswork — tell you what to do next.

We want every leap in what Agents can do to become real leverage for everyone — so you spend less time chasing tools and more time building what you actually care about.

Models will change. You shouldn't have to start over.

Thank you for showing up before Mirasim was fully ready. From here, we'll put these promises into every fix and every update, and work to earn your trust by making Mirasim more stable and more reliable.

— The Mirasim team

Mirasim
Get helpGet Mirasim

Acceptable Use Policy

Last updated: August 26, 2026

This Mirasim, Inc. ("Mirasim", "we", "us", or "our") Acceptable Use Policy (the "Acceptable Use Policy") sets out the rules for use of Mirasim and any related agents, sandboxes, tools and features (collectively, our "Services"). By accessing or using our Services, either as an organization or as an individual, you ("user(s)", "you", or "your") acknowledge that you have read and agree to be bound by this Acceptable Use Policy. This Acceptable Use Policy is incorporated into, and forms part of, our Terms of Service (the "Terms"). Capitalized terms used but not defined in this Acceptable Use Policy have the meanings ascribed to such terms in the Terms. If you have any questions about this Acceptable Use Policy, please contact us at support@mirasim.ai.

1. General#

Our Services execute code and take actions on your instruction, including autonomously and over multiple steps. This Acceptable Use Policy sets out what is and is not acceptable conduct when doing so. We may update this Acceptable Use Policy from time to time to reflect changes to our Services or to applicable laws, and your continued use of the Services following an update constitutes your acceptance of it.

Where you have (or we reasonably believe you have) breached this Acceptable Use Policy, we may, at our discretion, do any or all of the following:

  • Issue a warning regarding your conduct.
  • Suspend, throttle or terminate any session, agent, sandbox, container, API key or network access, in each case immediately and without prior notice where we reasonably believe there is an active attack, abuse of compute resources, or a threat to our infrastructure, to other users or to any third party.
  • Remove or disable access to the relevant content, project or workspace.
  • Restrict your use of certain functions, or suspend or terminate your account without refund, and revoke any invitation, referral or plan entitlement associated with it.
  • Preserve and disclose account records, session logs, IP addresses and network records where lawfully required, or where we reasonably believe disclosure is necessary to protect our rights or the safety of others.
  • Where we reasonably believe that you have committed a crime or are otherwise required to do so under applicable laws, notify and cooperate with appropriate governmental and/or law enforcement authorities in the relevant jurisdiction.

While we will aim to apply this Acceptable Use Policy consistently across all jurisdictions, in some jurisdictions there may be specific requirements under applicable laws which necessitate differing application of parts of this Acceptable Use Policy. You may contact us at support@mirasim.ai if you have any questions about actions taken against you in accordance with this Acceptable Use Policy.

2. Your Responsibility for Your Sessions, Agents and Keys#

You are responsible for all activity, code execution, network traffic, API calls and outbound communications originating from your account, sessions, agents, sandboxes, containers, connected accounts and API keys, whether initiated by you, by a member of your organization, or by an agent acting on your behalf. Delegating a task to an agent does not reduce your responsibility for what that agent does.

You must:

  • Scope credentials, tokens and permissions to the minimum necessary for the task, and never supply an agent with credentials or access that you are not authorized to use.
  • Supervise agent activity, and independently review and test outputs before relying on them or deploying them to any live system.
  • Keep your account credentials secure, and promptly notify us at support@mirasim.ai of any unauthorized use of your account.

3. Authorized Use Only: No Attacks, Intrusion or Interference#

You may direct the Services only at systems, networks, accounts, applications and data that you own or for which you hold documented authorization from the owner. You must not use the Services — including any agent, terminal, sandbox, simulated user, script or network access made available through them — to:

  • Scan, probe, fuzz, enumerate or otherwise test the security or availability of any system without prior written authorization from its owner.
  • Gain or attempt to gain unauthorized access to any system, account, network or data, including by exploiting vulnerabilities, brute force, credential stuffing, session hijacking, or the use of credentials you are not authorized to use.
  • Develop, host, distribute or operate malware, ransomware, spyware, keyloggers, rootkits, botnets, command-and-control infrastructure, exploit kits, or any tooling whose primary purpose is unauthorized access to systems or data.
  • Conduct or facilitate denial-of-service, amplification, or other volumetric or resource-exhaustion attacks.
  • Operate phishing pages, fake login or payment flows, spam infrastructure, or unsolicited bulk email or messaging.
  • Circumvent authentication, rate limits, CAPTCHAs, paywalls, digital rights management, robots.txt or any other access control of a third-party service.
  • Scrape, crawl or harvest data from any third-party service in breach of that service’s terms, or collect personal data at scale.
  • Interfere with, disrupt or overburden any third-party system, or any other user’s use of our Services.

Authorized security work. Nothing in this section prohibits testing systems that you own, or testing conducted within the documented scope of a written engagement or a published bug bounty program. You remain responsible for staying within that scope, and you may not use our infrastructure as the source of traffic directed at any third party without that party’s authorization.

4. Platform and Compute Integrity#

You must not:

  • Escape, or attempt to escape, any sandbox or container, or obtain or attempt to obtain elevated privileges on our infrastructure.
  • Tamper with or attempt to circumvent usage metering, quotas, credits, entitlements or other technical restrictions.
  • Create multiple or automated accounts, or manipulate invitations or referrals, in order to obtain access, rewards or resources that you would not otherwise be entitled to.
  • Share, resell, sublicense, rent or lease access to the Services, or directly or indirectly charge others for access to them.
  • Mine cryptocurrency, or operate proxies, VPN or Tor exit nodes, file-sharing or media streaming services, or any other workload unrelated to software development, using our compute.
  • Reverse engineer, decompile or disassemble the Services, except to the extent that applicable laws and regulations do not allow us to prevent you from doing so, or use the Services or their outputs to develop, train or benchmark a competing product or model.
  • Misrepresent the source or ownership of, or remove, obscure or modify any copyright, trademark or other proprietary notice in, any part of the Services.
  • Directly or indirectly suggest our support or endorsement of any product, service or content.

5. Third-Party Model Providers and Connected Accounts#

The Services route your inputs to third-party model providers and may connect to third-party services, repositories and tools that you authorize. You must comply with the terms and usage policies of those providers and services, and you must not use our Services to circumvent, jailbreak or evade their safety systems, usage restrictions, rate limits or geographic restrictions, or to generate content that those policies prohibit. Where you connect your own provider account or API key, you remain solely responsible for all use of that account and for compliance with that provider’s terms.

6. Data You Bring Into the Services#

You must not upload to, process in, or generate through the Services:

  • Personal data of third parties that you are not authorized to disclose or process.
  • Protected health information, payment card data, biometric identifiers, government identification numbers, children’s personal data, or any other data subject to heightened regulatory requirements, unless we have expressly agreed otherwise in writing.
  • Credentials, keys, confidential information, source code or other material that you do not have the right to use or disclose.
  • Any material that was procured via hacking or other illegal or unethical means.

7. Service Data and No Obligation to Monitor#

In order to operate, secure, support and improve the Services, we collect and process data relating to your use of them, including account and session metadata, resource and network usage, agent and tool activity, diagnostic and error data, and abuse signals. We may analyze this data to detect and investigate suspected violations of this Acceptable Use Policy, to protect our infrastructure, our users and third parties, and to maintain and improve the performance, reliability and quality of the Services. We handle such data in accordance with our Privacy Policy.

We have no obligation to monitor use of the Services, and we do not undertake to review, screen or verify any content, code, agent action or output. We may, but are not required to, investigate reports that we receive. Any monitoring or investigation that we do carry out is undertaken for our own purposes, and you should not rely on it as a control over your own use of the Services.

8. Prohibited Content and Applications#

You must not use the Services to create, host, process or distribute content, or to build, test or operate applications, that:

  • Sexualize or exploit minors, or facilitate child sexual abuse material.
  • Threaten, incite or facilitate violence, terrorism or other serious criminal activity, or provide instructions for producing weapons, including chemical, biological, radiological or nuclear weapons.
  • Promote or encourage suicide, self-injury or serious harm to others.
  • Harass, bully, defame or unlawfully discriminate against any person or group, including through hate speech.
  • Facilitate fraud, scams, money laundering, counterfeiting, or the sale of illegal or unlawfully procured goods or services.
  • Constitute synthetic or manipulated content intended to deceive, confuse or harm others, including deepfakes, impersonation of a real person or organization, or the presentation of outputs as human-created or independently verified when they are not.
  • Generate or disseminate disinformation, or coordinate or participate in inauthentic behavior.
  • Infringe the intellectual property, privacy, publicity or other rights of any person.

High-risk applications. Without our prior written agreement, you must not use the Services to build, test or operate systems for: the control of critical infrastructure; medical diagnosis or treatment decisions; weapons development or military targeting; law enforcement, criminal justice, migration, asylum, biometric surveillance or social scoring; or fully automated decisions producing legal or similarly significant effects on individuals.

9. Applications You Make Available to Others#

If you make an application built with the Services available to any other person, you are solely responsible for that application, including for providing your own terms of service and privacy notice, for complying with applicable laws (including any artificial intelligence disclosure requirements), for securing the application, and for ensuring that your end users are not given access to our infrastructure, credentials or quotas.

10. Export Control and Sanctions#

You must not use, or permit any person to use, the Services in violation of applicable export control, sanctions or trade laws, including by making the Services available to any person or entity located in an embargoed territory or identified on any applicable restricted-party list.

11. How to Contact Us#

Please contact us at support@mirasim.ai to report any breach (or suspected breach) of this Acceptable Use Policy, to report a security vulnerability in the Services, or if you have any other questions regarding this Acceptable Use Policy. Where you are making a report, please include a description of the issue and, where relevant, screenshots, URLs, timestamps and any account, project or session identifiers.