Draft early-access terms

Operating boundaries for the RepoShip preview

This draft records the product boundaries visible in the current code. It is not a complete agreement and is not ready to govern a public service.

Early-access scope

These are operating boundaries for the current preview, not final contractual terms.

RepoShip currently accepts allowlisted repositories and supports a narrow static React/Vite deployment path. Other detected runtime shapes can be analyzed but are not admitted to v1 deployment.
Features, quotas, integrations, and supported deployment targets may change during early access. No service-level agreement or availability commitment is offered for this preview.
The operator has not yet supplied final support, suspension, termination, data-export, or account-deletion processes.

Your repositories and access

Only connect systems and content that you are permitted to use.

You must have authority to install the GitHub App, authorize the user grant, read the selected repository, run its build commands, and publish its output.
You remain responsible for repository code, dependencies, licenses, environment values, domains, third-party accounts, and the legality of deployed content.
A private source repository can produce a public Cloudflare Pages deployment. Review generated output and the deployment plan before starting a build.

Acceptable use

The preview is not available for harmful, unlawful, or unauthorized workloads.

Do not use RepoShip for malware, credential theft, unauthorized access, abusive traffic, illegal content, rights infringement, or attempts to evade platform or provider controls.
Do not submit secrets, source, accounts, or infrastructure that you are not authorized to use, and do not interfere with other users or RepoShip systems.
Do not rely on this early-access service for workloads where interruption, data loss, or an incorrect deployment would create unacceptable safety, legal, or business risk.

Quotas, estimates, and third-party services

Admission controls bound the preview workflow; they do not replace provider terms or billing controls.

RepoShip may reject work when repository allowlists, account or repository quotas, concurrency, retries, managed-resource counts, or modeled cost ceilings are reached.
Displayed cost estimates are planning estimates. They are not quotes, invoices, spending guarantees, or promises that a third-party provider will charge a particular amount.
WorkOS, GitHub, Cloudflare, and any configured infrastructure providers operate under their own terms and availability. Final responsibility, warranty, and liability language remains counsel-defined.

Launch terms still missing

Public availability remains blocked until the operator and counsel complete the contractual record.

Operator legal identity, contact channel, acceptance flow, effective and update dates, account eligibility, territory, and the final description of the service.
Intellectual-property and content-license terms, takedown handling, enforcement and appeal rules, suspension and termination rights, and post-termination export or deletion.
Billing, taxes, refunds, renewals, support, SLA, warranties, disclaimers, liability limits, indemnity, governing law, venue, and dispute-resolution terms.

A working legal contact and verified deletion-request process are still operator-defined; the current contact page does not publish an operator address.

Review the current contact status