Browse documentation

Service information

Acceptable use

Keep Arvumi safe for other customers and the people who use your applications.

On this page

Updated November 3, 2026. This policy applies to applications, deployments, databases, and use of Arvumi’s services. Report suspected abuse to support@arvumi.com, using the reporting guidance.

Use the service responsibly

Host projects you have permission to operate and content you have permission to distribute. Follow applicable law and protect people who use your applications. You are responsible for your users, application authentication, dependencies, credentials, and reasonable controls against abuse of your endpoints.

Prohibited activity

  • Illegal content or activity, including sexual exploitation of children, trafficking, or distribution of stolen information.
  • Malware, phishing, credential theft, fraud, impersonation intended to deceive, or unsolicited bulk messaging.
  • Denial-of-service attacks, unauthorized access or scanning, exploitation of other systems, or attempts to access another customer’s code, secrets, logs, or data.
  • Content that infringes intellectual-property rights or unlawfully exposes personal information.
  • Cryptocurrency mining, botnets, abusive proxy or relay services, and workloads designed to exhaust shared compute, storage, network, or database capacity.
  • Evading billing, quotas, suspensions, or signup limits through repeated accounts, multiple identities, team creation, deletion, or other circumvention.
  • Disabling security boundaries or interfering with the service, operators, providers, or other customers.

Beta capacity and limits

Capacity is shared and finite. Plan ceilings do not reserve hardware. During beta, a GitHub identity can own at most three teams and create at most three teams in a rolling 30-day period across Free and Pro. Deleting teams or recreating an account does not reset that allowance. Do not obtain additional identities to evade these limits.

Handling violations

Arvumi may investigate reports and restrict or suspend affected workloads or accounts, including promptly when necessary to protect the platform or others. Retained operational, accounting, and anti-abuse records can support investigations. Contact support if you believe a restriction is mistaken or need help removing abusive content. Security research must stay within systems and data you are authorized to test; report suspected vulnerabilities without accessing other customers’ information.