Patternis terms of service
Effective date of this version: 16 October 2026
Part A. Cover Page
This Agreement is between Astra Forge LLC and the company or person accessing or using the Cloud Service. This Agreement consists of: (1) the Order Form below and (2) the Framework Terms defined below. If you are accessing or using the Cloud Service on behalf of your company, you represent that you are authorized to accept this Agreement on behalf of your company. By installing, accessing, or using the Product, Customer indicates its acceptance of this Agreement and agrees to be bound by the terms and conditions of this Agreement.
A.1 Order Form
| Field | Patternis |
|---|---|
| Framework Terms | This Order Form is governed by the Key Terms in A.2 and by the Common Paper Cloud Service Standard Terms Version 2.1 incorporated by reference (Part B). If this Order Form and the Framework Terms conflict, this Order Form controls. Any modifications to the Standard Terms made in this Cover Page control over conflicts with the Standard Terms. |
| Provider | Astra Forge LLC, an Arizona limited liability company. Notices to Provider: legal@patternis.dev. |
| Customer | The GitHub user or organisation account on which the Patternis GitHub App is installed, and the person accepting on its behalf, who must be 18 or older. Patternis is offered during the beta only to Customers located in the United States and only for business or professional work. An individual may be Customer on a personal GitHub account, and may subscribe, if they meet those conditions. |
| Cloud Service | Patternis: the Patternis GitHub App and the service at https://api.patternis.dev. As the Cloud Service is currently built, when a qualifying event occurs in a repository Customer has installed the App on, the service decides whether and how to act, starts the patternis-runner.yml workflow in Customer's own repository on Customer's own GitHub Actions runner, records each decision to act or to refuse in a ledger (events that are not requests for work, such as edited comments, are ignored without a record), of which a workflow in one of Customer's repositories can read at GET /receipts the receipts recorded for that repository, by GitHub's repository number, while it belonged to Customer's account (Other Changes item 4), and may post a short receipt or notice on the issue or pull request. The AI work runs on Customer's runner using Customer's own AI provider key; the service does not contact an AI provider. Provider may change how the Cloud Service works, and the Documentation. |
| Documentation | The setup page at https://patternis.dev/setup and the workflow file at https://patternis.dev/patternis-runner.yml (the same paths are served at https://api.patternis.dev), as Provider updates them. The Documentation describes how the Cloud Service currently works so that Customer can set it up and use it. Nothing in it is a warranty or commitment by Provider, and Provider may change it. |
| Order Date | The date Customer accepts these terms. Customer accepts them by installing, accessing or using Patternis: the homepage, the setup page and the App's GitHub listing each say "By installing or using Patternis you agree to the Terms". For a paid subscription Customer accepts them again by ticking the required box accepting these terms on Stripe's payment page before subscribing. |
| Pilot (free trial) | Free trial. The Pilot Period ends at 15 days or 250 units, whichever comes first. Eligibility is checked by GitHub login. The service keeps a reduced trial-used record (login and trial dates) for 24 months after trial end and refuses another trial under the same login while that record remains. A GitHub-reported rename is followed while the record remains linked to an installed App. The reduced record does not contain GitHub's numeric account id, so a rename after uninstall may not follow it; a later installation under the new login may be treated as eligible. No payment method is requested for the trial. Modifying the Common Paper Order Form, the Subscription Period does not start automatically when the Pilot Period ends. It starts only if Customer subscribes. If Customer subscribes during the Pilot Period, Customer's work counts toward the first billing month's allowance, the first fee is charged on the day the Pilot Period would have ended, and the Subscription Period starts that day. If that day is less than about two days away when Customer subscribes, or the trial units are used up, the Subscription Period starts and the first fee is charged on the day Customer subscribes. Stripe's payment page shows which applies before Customer pays. If Customer uses the whole allowance before the first fee is charged, new work resumes when the second billing month begins. If the subscription ends before the first fee is charged, the Pilot Period ends with it and does not resume. Modifications that apply only to the Pilot Period: (1) Sections 6.3, 6.4 and 9.1 do not apply. (2) There are no Increased Claims or Unlimited Claims. (3) The General Cap Amount is $100 for claims that arise during the Pilot Period. (4) Either party may immediately terminate the Agreement during the Pilot Period for any or no reason by giving notice. |
| Subscription Period | One month, renewing monthly. |
| Cloud Service Fees | USD 20 per installation per month, plus tax where it applies. An installation is one installation of the Patternis App on one GitHub account; GitHub allows one per account, and a subscription is bound to one installation. A subscription includes up to the monthly unit allowance in A.3 item 4. Provider may change the fees by posting the change on patternis.dev, with the date it takes effect, and giving Customer notice at its Notice Address, at least 30 days before that date. The change applies from Customer's first renewal on or after that date, and Customer may cancel before then. |
| Customer's own costs | Customer's AI provider usage is billed by Customer's provider to Customer's own account, under Customer's own agreement with that provider. GitHub Actions usage is billed by GitHub under Customer's GitHub plan. Provider does not pay, pass through or mark up either. When the cheapest capable tier has no remaining capacity, the service may route one tier up, which costs more on Customer's key; the units charged by Patternis do not change with tier. |
| Payment Process | Automatic monthly payment through Stripe. Customer subscribes on Stripe's payment page and pays through Stripe Managed Payments, in which Link is the merchant of record. Customer authorizes the monthly charge. Stripe handles payment disputes and transaction support. Fees paid through Link are Fees paid by Customer to Provider under these terms. If a monthly payment fails, the Cloud Service continues for 7 days while Stripe retries it, then pauses until Stripe reports the payment, and the service may say so in a comment. The same applies when Stripe cannot collect a monthly invoice for another reason, including the first fee after the Pilot Period. A disputed charge has no grace period. |
| Auto-renewal / Non-Renewal Notice Date | Renews monthly. The Non-Renewal Notice Date is the end of the current Subscription Period. Either party may decline renewal at the end of that period. Customer may cancel at link.com; after cancelling, the Cloud Service continues to the end of the month already paid for. Except for prorated refunds the Standard Terms give with specific termination rights, Provider does not refund part of a month; Link may issue refunds under its own terms. Provider may refund a fee, at its discretion, when the Cloud Service failed. Uninstalling the App does not by itself cancel the subscription at Stripe. When Customer uninstalls, Provider is notified and may cancel the subscription so that it ends at the end of the month already paid for; Customer can also cancel at link.com. If the same GitHub account installs the App again, the subscription moves to the new installation. |
| Use Limitations | See A.3. |
| Technical Support | None. Customer may write to support@patternis.dev; no response or response time is promised. |
| SLA | None. No uptime or response-time commitment is made. |
| Professional Services | None. |
| Other Changes to Standard Terms (this Order Form) | The Pilot modifications and when the Subscription Period starts (Pilot), the fee-change rule (Cloud Service Fees) and the refund rule (Auto-renewal) above; the Notice Address in A.2 (Section 12.9); and the changes listed under "Other Changes to Standard Terms" in A.2, items 1 to 13. |
A.2 Key Terms
| Field | Patternis |
|---|---|
| Effective Date | The Order Date. |
| Governing Law | The laws of the State of Arizona. |
| Chosen Courts | The state and federal courts located in Pima County, Arizona. |
| Covered Claims | Provider Covered Claims: None. Customer Covered Claims: Any action, proceeding, or claim that (1) the Customer Content, when used according to the terms of the Agreement, violates, misappropriates, or otherwise infringes upon anyone else's intellectual property or other proprietary rights; or (2) results from Customer's breach or alleged breach of Section 2.1 (Restrictions on Customer). |
| General Cap Amount | 1x the Fees paid or payable by Customer to Provider in the 12 month period immediately before the claim (at USD 20 a month, at most USD 240). During the Pilot Period, $100 (A.1, Pilot). |
| Increased Claims | None. |
| Increased Cap Amount | None, since there are no Increased Claims. |
| Unlimited Claims | None. At all times, including the Pilot Period, these terms do not limit liability that the law does not allow to be limited, such as liability for fraud. |
| Additional Warranties | By Provider: None. By Customer: None. |
| Notice Address | For Provider: legal@patternis.dev. Provider holds no email or postal address for Customer. Provider gives notice by opening an issue in one repository the App is installed on. If Customer has uninstalled the App, notice is posted on https://patternis.dev. Modifying Section 12.9, notice is given when the issue is opened or the notice is posted. |
| DPA | None is in place when Customer accepts these terms. Section 3.1 of the Standard Terms applies. Customer can ask for one at legal@patternis.dev; Provider enters into a DPA when and as the law requires, using Common Paper's standard Data Processing Agreement. |
| Security Policy | None. |
| Insurance Minimums | None. |
| Customer Content (clarifying the Standard Terms definition for this Cloud Service) | Customer Content means the data submitted to the Product by or on behalf of Customer or Users. For Patternis that is: (a) the event notifications GitHub delivers for repositories Customer installs the App on, which include account and repository identifiers, issue and pull-request numbers and size counts, and the titles, descriptions and comment text people write there; and (b) the receipt and capacity reports Customer's workflow sends back. As the Cloud Service is currently built: Provider reads the text in (a) in memory only, to detect an @patternis request and to size the task, and does not store it; Provider stores the identifiers, reason codes and receipt fields described in its Privacy Policy; and the Product does not receive Customer's repository contents or diffs, Customer's AI provider key, the prompt sent to Customer's AI provider, or the AI output, which is written only to Customer's own workflow run. Text people choose to paste into issues, descriptions or comments reaches Provider as part of (a), whatever it contains. |
| Other Changes to Standard Terms | 1. Machine Learning (Section 1.6). Section 1.6's statements that AI-generated information may be incorrect or inaccurate and is not a substitute for human oversight also apply to output Customer's own AI provider produces through the Cloud Service. |
| 2. Customer's AI provider. Customer's AI provider is a third-party service used under Customer's own agreement with it. Customer is responsible for holding a provider API key it is permitted to use in automation, for complying with the provider's terms, and for all provider charges. Provider is not responsible for the provider's availability, charges or output. | |
| 3. Actions in Customer's repositories. Customer authorizes Provider to start the Patternis workflow in, to post receipts and notices as comments on issues and pull requests in, and, to give Customer notices under the Agreement, including of a security breach, to open an issue in, the repositories Customer installs the App on. On a public repository those comments and issues are public. | |
4. Ledger access. As currently built, a workflow in a repository can read, at GET /receipts, the receipts recorded for that repository by GitHub's repository number, while it belonged to Customer's account, and no others, and only when GitHub confirms the workflow's account is the account the App is installed on. Receipts written before migration 0004 record no repository number and no workflow can read them. Customer controls who can run workflows in its repositories. | |
| 5. Deletion (Section 5.5). Modifying Section 5.5 (Effect of Termination), clause (b) is replaced by this: Provider deletes Customer Content when and as the law requires. The Privacy Policy describes Provider's current retention practice, which can change. | |
| 6. Changes to these terms (Section 12.2). Modifying Section 12.2, Provider posts a material change on patternis.dev, with the date it takes effect, at least 30 days before that date, and opens an issue announcing it in one repository of each installation with a paid subscription. The current version is at https://patternis.dev/terms. A posted change applies to Customer from Customer's first renewal on or after its effective date; Customer who does not accept it can cancel at link.com before then. Section 12.2 otherwise applies. | |
| 7. Suspension (Section 2.2). Modifying Section 2.2, Provider may suspend Customer's access, with or without notice, while a Fee is unpaid, disputed, or cannot be confirmed. The 7-day grace in the Payment Process applies to a failed or uncollectible monthly invoice; disputes receive no grace. If a Fee is refunded or reversed, Provider may end the Subscription Period it paid for. The sentence beginning "However, Provider will try to inform Customer" does not apply. | |
| 8. Usage Data (Section 1.4). Modifying Section 1.4 (Feedback and Usage Data), Provider may also disclose Usage Data to the service providers named in the Privacy Policy, to run the Cloud Service; in the comments, issues and workflow runs item 3 authorizes; and as the law requires. | |
| 9. Payment (Sections 4.3, 4.6 and 5.5). Modifying Sections 4.3 (Automatic Payment), 4.6 (Payment Dispute) and 5.5 (Effect of Termination): Link, as merchant of record, charges the payment method Customer gives on Stripe's payment page and provides Customer's receipts and invoices; Provider does not itself charge Customer or provide copies of Customer's bills, and Section 5.5(d) does not apply. The parties are not required to resolve a payment dispute within 15 days; charge disputes are handled by Stripe and Link. | |
| 10. Warranties (Section 6). Modifying Section 6 (Representations & Warranties), clause (c) of Section 6.1 (Mutual) applies to Customer only, and Sections 6.3 (Representations & Warranties from Provider) and 6.4 (Provider Warranty Remedy) do not apply. | |
| 11. Damages (Section 8.4). Modifying Section 8.4 (Exceptions), Section 8.2 (Damages Waiver) also applies to a breach of Section 10 (Confidentiality). | |
| 12. Confidentiality (Sections 10.3 and 10.4). Modifying Section 10.3 (Required Disclosures), a Recipient may disclose Discloser's Confidential Information to the extent required by Applicable Laws without the conditions that section sets, and gives Discloser notice of the disclosure only when and as the law requires. Modifying Section 10.4 (Permitted Disclosures), Provider may also disclose Customer's Confidential Information to the service providers named in the Privacy Policy, under their standard terms, to run the Cloud Service. | |
| 13. Other documents. Modifying the definitions of Framework Terms and Order Form in Section 13 (Definitions): the Privacy Policy at https://patternis.dev/privacy, and any page other than this Cover Page and the Documentation, describe Provider's current practices. They are not part of the Agreement, and Provider may change them. References to them in this Cover Page identify them and do not incorporate them. |
A.3 Use Limitations
Each item describes how the service currently works; Provider may change it (A.1, Cloud Service).
- Setup Customer performs. The workflow file must be on the repository's default branch at
.github/workflows/patternis-runner.yml, and the repository secretPATTERNIS_PROVIDER_KEYmust hold Customer's own API key. Version 1 supports Anthropic keys only and refuses any other key shape. - What starts billable work. Opening, reopening, pushing to, or marking ready a pull request; opening or reopening an issue; creating a comment in which a line begins with
@patternis. Each push to an open pull request is a new task. Edited or deleted comments, closed pull requests and labels are not. - Who can start it. For each event GitHub reports an author: of the pull request, of the issue, or of the comment. Work starts only when that author is the repository's owner, a member, or a collaborator. Otherwise the event is refused and nothing is charged, even when an owner, member or collaborator reopened or pushed to the pull request or issue; they can ask for the work with an
@patterniscomment instead. - Units. A pull-request review costs one unit per 100 changed lines, rounded up, plus one unit per changed file; issue triage costs one unit per 2,000 characters of the issue's title and description or, when an
@patterniscomment asks for it, of that comment, rounded up; a task whose size GitHub did not report costs 10 units; every task costs at least 1 and at most 60 units. A task that fails to start is not charged. A paid subscription includes up to 5,000 units in each billing month. Provider may raise the allowance for Customer on request to support@patternis.dev. When the account has used 80% in a billing month, the service may post a comment saying so. When it is used up, the service starts no new tasks for that installation until the next billing month and may say so in a comment. Unused units do not carry over. Work run after Customer subscribes and before the first fee is charged counts toward the first billing month's allowance. - Trial. 15 days or 250 units, whichever comes first. A retained trial-used record blocks another trial under the same GitHub login for 24 months after trial end; see the Pilot row for the rename limitation. A task larger than the units remaining is refused rather than partly run.
- Size bound on Customer's side. The workflow truncates the diff or issue text to 100,000 bytes before sending it to Customer's AI provider.
- Units on receipts. Units are charged once, on a task's
dispatchreceipt, and a failed dispatch is charged nothing. A workflow reads only its own repository's dispatch receipts (A.2 item 4). Dispatch receipts written before migration 0004 have no repository number and no workflow can read them. The monthly unit count Provider keeps for the allowance equals the sum of the account's dispatch receipts for the billing month, except that receipts deleted at Customer's request no longer appear while the count still includes them.
Part B. What these terms incorporate by reference
Incorporated: the Common Paper Cloud Service Standard Terms, Version 2.1, at https://commonpaper.com/standards/cloud-service-agreement/2.1/, as modified only by the Cover Page: the Order Form in A.1 (the Pilot modifications and when the Subscription Period starts, the fee-change rule and the refund rule), the Notice Address in A.2 (Section 12.9), and "Other Changes to Standard Terms" in A.2, items 1 to 13. Common Paper's Terms of Service, its click-through form of this agreement, incorporates the same Standard Terms at the same URL. Common Paper's version history lists Version 2.1 as released 4 November 2024; the 2.1 page itself says 5 November 2024. Common Paper states that a hosted version stays unchanged at its URL and that later changes are issued as new versions at new URLs.
Sections incorporated, by Common Paper's headings (all thirteen, none excluded):
| Section | Heading | Touched by these Key Terms |
|---|---|---|
| 1 | Service | 1.2: Technical Support is None; 1.4: Usage Data may also go to named service providers, in authorized comments, issues and runs, and as the law requires (A.2 item 8); 1.5 Customer Content clarified; 1.6 Machine Learning: Common Paper's default applies, and its warning about AI output also covers Customer's own AI provider (A.2 item 1) |
| 2 | Restrictions & Obligations | 2.2: suspension also while a Fee has failed, is unpaid or disputed, or cannot be confirmed, with or without notice (A.2 item 7) |
| 3 | Privacy & Security | 3.1 DPA: none in place; Provider enters into Common Paper's DPA when and as the law requires (Key Terms). Security Policy: None |
| 4 | Payment & Taxes | 4.1 kept: the Order Form's refund rule keeps the prorated refunds 4.1 allows, and adds that Provider may refund a fee at its discretion when the Cloud Service failed; 4.3 and 4.6: Link charges and bills, and no 15-day resolution period (A.2 item 9) |
| 5 | Term & Termination | 5.1 Non-Renewal Notice Date set in the Order Form; the Subscription Period does not start automatically after the Pilot; 5.5(b) replaced by deletion when and as the law requires (A.2 item 5); 5.5(d) does not apply (A.2 item 9) |
| 6 | Representations & Warranties | Additional Warranties: None; 6.1(c) applies to Customer only; 6.3 and 6.4 do not apply (A.2 item 10, and the Pilot) |
| 7 | Disclaimer of Warranties | |
| 8 | Limitation of Liability | caps set in Key Terms; during the Pilot, $100 and no Increased or Unlimited Claims; 8.2's damages waiver also covers a breach of Section 10 (A.2 item 11) |
| 9 | Indemnification | Provider Covered Claims: None, so 9.1 does not apply; Customer Covered Claims at Common Paper's default; 9.1 is also excluded during the Pilot |
| 10 | Confidentiality | 10.3 and 10.4 modified (A.2 item 12) |
| 11 | Reservation of Rights | |
| 12 | General Terms | 12.2: the fees may change on 30 days' notice, posted on patternis.dev and given at the Notice Address (Order Form, Cloud Service Fees); these terms may change on 30 days' notice posted on patternis.dev, with an issue announcing the change in one repository of each installation with a paid subscription (A.2 item 6); either change applies from Customer's next renewal, and Customer may cancel first; 12.9: notices to Customer by an issue in its repository or a notice on patternis.dev (Notice Address) |
| 13 | Definitions | the Privacy Policy and other pages are not part of the Framework Terms or the Order Form (A.2 item 13) |
Fields kept at Common Paper's defaults (Customer Covered Claims, the 1x General Cap Amount and Pilot modifications (2) to (4)) carry Common Paper's default wording from the CSA Cover Page. Pilot modification (1) is narrowed from Common Paper's wording to Sections 6.3, 6.4 and 9.1, so that Customer's protection of Provider under Section 9.2 applies during the Pilot too.
Attribution, to appear on the published Cover Page and kept on every copy:
Common Paper Cloud Service Agreement (Version 2.1) free to use under CC BY 4.0.
With: a link to the Standard Terms URL above; a link to the licence, https://creativecommons.org/licenses/by/4.0/; and a changes notice, because CC BY 4.0 asks that modifications be indicated:
This Cover Page was adapted by Astra Forge LLC from the Cover Page of Common Paper's Terms of Service for the Cloud Service Agreement, with the Pilot field of the Cloud Service Agreement's Order Form; its opening paragraph is the Terms of Service's, naming Astra Forge LLC and with "installing" in place of "signing up". The Standard Terms are incorporated by reference. This Cover Page modifies them in: the Order Form's Pilot field (when the Subscription Period starts, and the four Pilot modifications, the first narrowed to Sections 6.3, 6.4 and 9.1), Cloud Service Fees (how the fees change) and Auto-renewal (refunds); the Key Terms' Notice Address (Section 12.9); and the Key Terms' "Other Changes to Standard Terms", items 1 to 13, which modify Sections 1.4, 1.6, 2.2, 4.3, 4.6, 5.5, 6.1, 6.3, 6.4, 8.4, 10.3, 10.4 and 12.2 and the definitions of Framework Terms and Order Form.
Common Paper's own guidance is that the Cover Page may be customised freely but must keep the licence information and the link to the Standard Terms, and that changes to the Standard Terms belong in the Cover Page rather than in edits to the Standard Terms.