Terms of Service

Service and operator

gerberize is operated by Sovereign ATX LLC in Austin, Texas. Contact: kavinlingham1@gmail.com.

gerberize provides CLI, MCP, and API tools for PCB validation, simulation, manufacturing exports, account management, and guarded ordering workflows. The current hosted release is a developer preview. Fabrication ordering is sandbox-only, and configured Stripe payments and subscriptions are test-only. The service does not currently submit live manufacturing orders or collect live subscription payments.

Accounts and agent access

Google sign-in creates or accesses an owner account when configured. Existing accounts require explicit owner-authorized linking rather than automatic merging by email. Advanced owner-key access remains available for provisioned accounts.

Keep your Google account, owner keys, agent keys, and devices secure. Authorize only CLI device codes you recognize. Give agents their own scoped keys, and revoke keys or sessions you no longer need. Agent credentials cannot change account controls, raise spending limits, or approve their own order requests.

You are responsible for deciding which agents and tools may act through your credentials and for reviewing their work. A browser sign-out does not revoke agent keys. Account sessions and agent keys have separate revocation controls.

Files, tool results, and engineering decisions

Submit only files and information you have permission to use with the service. Cloud commands transfer their inputs to the backend for processing and storage; local checks run on your machine. Your selected MCP client or AI-agent provider has its own behavior and terms.

Validation and simulation produce findings from supported inputs, rules, models, and installed tools. They can report unsupported inputs, partial results, warnings, or errors. A successful result is not certification of electrical safety, regulatory compliance, manufacturability, or fitness for a particular product. Review the design, simulation assumptions, exact components, fabrication requirements, and generated output before relying on them or releasing hardware.

Keep your own copies of source designs and required results. The current service exposes account exports, but does not provide an agreed backup, uptime, completion-time, or recovery service level.

Free and Pro cloud allowances

Free and Pro have configurable monthly cloud-job allowances. The workspace displays the account's current allowance, usage, and reset time from the server. Jobs created during the UTC calendar month count toward usage, including jobs that later fail. Local commands are not metered by these cloud allowances.

The current defaults are 10 cloud jobs per month on Free and 100 on Pro; the deployed configuration determines the actual limits. An explicit account-specific unlimited grant can override the cloud quota without creating a paid subscription or granting that allowance to other accounts. Exhausting the allowance blocks new cloud jobs and does not block local checks.

Pro pricing is not yet set for a public paid launch. When configured, the workspace displays the recurring test price obtained from Stripe before directing you to hosted Checkout. Unavailable billing actions remain disabled. Do not enter real payment details in a test payment flow.

A Checkout return page alone does not grant Pro. The server verifies the configured subscription and its active period. Subscription management and cancellation use Stripe's hosted billing portal when available. A subscription marked to cancel at the end of an active billing period can retain Pro until that period ends. No refund rule or future live payment obligation is established by this test-only release.

Sandbox orders and spending controls

Ordering requires a saved, valid quote, a per-order cap, and a monthly budget. Requests over the approval threshold require an owner-approved, expiring token for that quote. Approval does not override spending caps or itself place an order. Stable idempotency keys protect supported retries from duplicate submissions.

Subscriptions and cloud allowances are separate from fabrication payment settings and spending caps. Pro does not authorize fabrication spending. The built-in sandbox fabricator does not contact a manufacturer. External integrations may be unavailable, credential-gated, or limited to sandbox quote/status operations; the integration status and returned errors describe those limits.

Ending access and requesting data

You can stop using the service, revoke agent keys, revoke browser sessions, or request account deactivation. A subscription or pending Checkout must be resolved, queued or running jobs completed, and outstanding orders resolved before the account can be deactivated. Deactivation revokes access and does not erase stored account, uploaded-file, job, order, or billing history.

Account settings provide an export of supported records and files, subject to interactive size limits. Contact kavinlingham1@gmail.com for help with larger exports, access issues, or deletion requests. Data handling is described in the Privacy Policy; these terms do not set a deletion deadline.