Professional setup — service terms

Seller and contact

ForgeFrame Labs is the public brand for independent software services operated from Poland. The responsible legal seller, applicable billing information and agreed service details are disclosed in the individual written scope confirmation before payment. Request these details at forgeframe.lab@gmail.com. Do not pay until the seller and scope are clear.

Included in the fixed-scope setup

• One GitHub repository with a valid existing OpenAPI 3.x specification in YAML or JSON.
• A pull-request GitHub Actions compatibility gate, using an audited immutable Action reference.
• Configuration of the baseline and a documented policy for explicit, time-limited exceptions.
• A demonstration of an additive change passing and a breaking change being blocked.
• Transfer of JSON/Markdown release evidence and concise operating instructions.

Excluded: building an API from scratch, modifying live server behavior, migration of multiple repositories, cloud hosting, ongoing monitoring, and certification of regulatory or runtime compatibility. Additional work requires a separate written quote.

Eligibility, ordering and delivery

Contact us before paying. We check specification format, repository permissions, CI runner compatibility, and any security constraints. We confirm a realistic delivery date and agreed scope by email. After the scope and delivery schedule are accepted in writing, we issue a unique Stripe-hosted payment link for that order in USD. The link is not published as an open checkout. Bank exchange rates may vary. Work begins only after confirmed payment and approved least-privilege access. Stripe displays the actual charged total before the customer authorizes payment. If we cannot accept a proposed repository or schedule, do not pay.

Do not email access tokens, passwords, secrets, confidential source files or full private API specifications. Any repository access must be granted through the platform's ordinary permission controls and may be revoked on completion.

Completion and acceptance

Delivery includes a Pull Request or agreed configuration artifact, at least one successful additive-change run and one deliberately blocked breaking-change run, plus the human-readable and JSON evidence outputs. The customer reviews these artifacts and confirms acceptance by email. If the configuration does not meet the written scope, report the discrepancy so it can be corrected before closure. Any follow-up support beyond the accepted scope requires a separate agreement.

Cancellation, refunds and statutory rights

If ForgeFrame Labs cannot deliver the agreed service, contact forgeframe.lab@gmail.com so the payment can be reviewed and refunded to the original payment method when appropriate. Requests received before work starts will normally receive a full refund. Once work begins, the outcome depends on the agreed scope, work completed and mandatory applicable law.

The setup offer is designed primarily for business customers. Any mandatory consumer protections — including applicable withdrawal rights — remain unaffected. We do not assume a customer has waived rights merely by paying. Where the law requires express consent to start services during a withdrawal period, that consent must be obtained separately.

Limitations and support

Contract Guard analyzes changes recorded in OpenAPI specifications. It does not test actual runtime compatibility, detect all undocumented behavior, or guarantee that downstream customers will not experience problems. We provide the agreed configuration and handover; a request for correction can be sent to forgeframe.lab@gmail.com.

Payments and privacy

Stripe processes card and payment-method details on its own hosted checkout. We receive only the transaction, customer and billing information necessary for fulfillment, customer support and legally required recordkeeping. See the ForgeFrame Labs privacy notice and Stripe privacy statement.