Browse documentation

Service information

Public beta terms

Understand beta availability, customer responsibilities, charges, cancellation, and data limits.

On this page

Updated November 3, 2026. These terms describe the public beta operated by Arvumi in Pennsylvania, United States. Contact support@arvumi.com about these terms or your service. By using Arvumi, you agree to these beta terms and the acceptable-use policy. The privacy information explains service data practices.

A service in active development

Arvumi is a public beta for hobby and noncritical projects. Features, limits, and availability can change. There is no uptime or support-response guarantee. Deployments, requests, builds, or databases can fail or become unavailable, and data can be lost. Do not rely on the beta for emergency services, safety-critical systems, or as the only copy of important data.

Shared capacity is finite. Plan ceilings limit a workload’s settings; they do not reserve hardware or guarantee that a build, function, or database can start. Requests can queue or fail when capacity is exhausted.

Accounts and teams

Use a GitHub account you control and keep account access and API keys secure. Team owners and admins are responsible for membership, repository grants, deployment settings, and billing actions they authorize. During beta, each GitHub identity can own at most three teams and create at most three teams in a rolling 30-day period, across Free and Pro. Existing teams above the limit remain usable. Deleting a team or recreating an account does not reset the creation allowance. Invitations do not create a separate allowance.

Your applications and data

You retain ownership of your content. You authorize Arvumi to check out repositories, build and store artifacts, run applications, process requests, and maintain operational copies as needed to provide the service. Only deploy content and dependencies you have permission to use, and follow applicable law and the acceptable-use policy.

You are responsible for application authentication, input validation, dependencies, secrets, and the data your application collects. A private repository does not make its deployed website private. Keep credentials out of static output and logs. Do not use the beta for data or workloads that require a certification, compliance commitment, or protection that Arvumi has not expressly agreed to provide.

Prices and payments

The pricing page and team Billing page show plan fees, usage prices, credits, and database packages. Prices are in USD before applicable tax. Credits apply to eligible usage, expire each period, and do not roll over. Plan fees and paid database packages are separate from usage credits. Review the displayed offer before purchasing or changing paid services.

Builds use allocated CPU and memory. Functions use configured CPU and memory over forwarded request duration, including activation, queueing, and streaming; warm idle time is free. Usage alerts and concurrency limits are not hard spending caps. A workload pause does not end subscription, retained-storage, or paid database-package charges.

Stripe processes payments and provides hosted invoices and subscription management. Use the customer portal from Billing to request cancellation and check its effective date. Cancellation does not erase accrued charges or delete your projects and databases. Database-package charges continue until deletion and access revocation are confirmed. Closing a team requests subscription cancellation and can wait for confirmation; remove retained resources as needed. Contact support for cancellation problems, disputed charges, or refund requests. Refunds are reviewed individually and are not guaranteed by this policy.

Backups and leaving the service

Keep your source code, database exports, and any necessary application data independently. Operational backups support platform recovery; they are not a customer restore guarantee, an export service, or a promise of any recovery point or recovery time. Temporary function files and module state are not durable storage.

Deleting projects, databases, teams, or an account may be irreversible. Deletion does not promise immediate removal from operational logs, backups, accounting records, or retained anti-abuse receipts. Contact support for account closure and privacy requests, and review the retention information.

Service restrictions and updates

Arvumi may restrict or suspend workloads or accounts for abuse, security problems, resource exhaustion, unpaid charges, or operational needs. Contact support to discuss a restriction. Material changes to these terms will be published on this page with an updated date. This service information does not claim that Arvumi is certified for a particular regulatory or industry standard.