Service terms

Version dated 31 October 2026

Progon is provided by Pavel Sergeevich Shumilin, an individual entrepreneur registered in Russia, registration number (OGRNIP) 326774600675502 and tax identification number (INN) 463230948130. In these terms, “we” and “us” mean this provider. “You” means the customer identified in the written order.

We accept enquiries from businesses and private individuals. We confirm whether we can serve your country and workload, and agree a lawful payment route, before accepting an order or receiving access to your project. The contact details in section 15 identify the contracting provider.

1. Your order and contract

1.1. Contact us on Telegram to discuss your project. We agree the service, repositories, server resources, work, total price, start date, term and payment arrangements in a written order. The order also identifies hosting and administrative access locations and any data-processing arrangements needed for your project.

1.2. After the eligibility checks, we send the final order and this version of the terms on Telegram. The contract is formed when you accept that order on Telegram and we confirm acceptance on Telegram. An enquiry, a website visit or an unsolicited payment does not form a contract. Payment is due as stated in the accepted order and before paid work begins.

1.3. If you order for a business, you confirm that you can bind it to the contract. If you act wholly or mainly outside your trade, business or profession, the consumer provisions apply to you to the extent required by applicable law. Describing an order as a business purchase does not remove rights you legally have as a consumer.

1.4. An expressly agreed order takes priority over these terms for its stated scope and price. Mandatory law and any applicable data-transfer clauses take priority where they require it. A change to this website does not change an accepted order.

2. What we provide

2.1. Progon supports GitHub Actions in private repositories with Linux jobs. Public repositories, macOS, iOS and Windows builds, GitLab and Jenkins are outside the standard service.

2.2. Managed server: we provide a dedicated physical server for your CI, configure and connect the first two repositories, and maintain the server during the service term. Other customers' jobs do not run on that server.

2.3. Your server: you rent and pay for hosting in your own name. We configure the server, connect and optimise CI for the first two repositories, verify the result and hand over the configuration. Ongoing support is optional.

2.4. Each plan covers one server and the workload its resources can support. We assess the workload before connection. More resources, another server or extra engineering work require a separate agreement. Adding repositories alone does not increase the monthly fee.

2.5. You retain your rights to your code and data. You authorise us to use them only as needed to deliver the agreed service. Third-party software remains subject to its own licence terms. We provide the configuration handover included in your order.

3. Trial, setup and support

3.1. Your agent can prepare a report of your existing CI using the measurement instructions on our website. We also offer one free CI run on our runner before payment. We agree access, permitted data and cleanup conditions before that run. It does not replace the measurements used for the performance refund in section 6.

3.2. We launch the managed service within one calendar day after payment and receipt of the agreed access. Setup on your server takes up to one calendar day after payment and receipt of server access. If you are a consumer who does not request an early start under section 7, these periods begin when your cancellation period ends. The order records the start date and any agreed dependency.

3.3. We give you the runner label. You create a temporary GitHub runner registration token and send it through the agreed channel. We register the runners, and you or your agent move the agreed jobs to them. You decide which jobs and repository secrets the workflows use.

3.4. Managed service and optional support include server monitoring, planned updates, restoration of the configured CI after failures and answers to service questions. We begin restoration within one business day after a failure. Jobs wait while the single server is unavailable. You can arrange fallback GitHub-hosted runners separately.

3.5. Business days are Monday to Friday, excluding public holidays at our registered place of business in Russia. The order records any agreed support hours. The standard service does not include a 24-hour support desk or a guaranteed uninterrupted service.

4. Prices and included work

4.1. Managed server costs USD 590 per month. It includes setup of the first two repositories, ongoing support and two hours of changes you request each month. There is no separate initial setup fee. Consumer withdrawal and early cancellation rights appear in sections 7 and 12.

4.2. Setup on your server costs USD 990 once. Optional support costs USD 330 per month per server and includes five hours of changes you request each month. Your hosting charges are separate and payable to your chosen host.

4.3. Additional repositories have a one-time connection price: USD 65 for standard connection, estimated at one hour; USD 195 for connection with adaptation, estimated at three hours; or from USD 390 for complex work under an agreed estimate. We confirm the tier and fixed scope before work starts.

4.4. We use the month's remaining included hours first. Before payment, the order records the hours credited and the balance due. We do not charge again for credited work or also deduct separately paid work from your included hours.

4.5. Extra work beyond included hours costs USD 65 per hour and starts only after you agree its scope and cost. Initial setup, monitoring, planned updates, restoration of configured CI and correction of our setup errors do not use the included change hours. Unused hours do not carry over.

4.6. We complete the agreed scope for its fixed price even if we underestimated the work. We charge more only for a scope increase you approve in advance. Monthly fees change only by agreement for increased server resources, an additional server or more engineering work.

5. Taxes, payment and acceptance

5.1. Prices are quoted in US dollars. For consumers, the listed prices include any taxes we are legally required to collect. Before you accept, the order states the total payable, any agreed additional work, tax treatment, settlement currency and any agreed exchange rate or conversion method. Business orders state any applicable tax or reverse-charge treatment. A USD quote does not promise that a particular bank, card or payment service is available.

5.2. We confirm a lawful payment and refund route before accepting the order. Pay only using the instructions in that order and invoice. We do not ask you to conceal the seller, the purpose or origin of a payment. Any mandatory charge we impose is included in the consumer total before acceptance. Your own bank may charge separately under its agreement with you.

5.3. Managed service and optional support are invoiced monthly in advance. Managed invoices are due within five business days of issue unless the order agrees another due date. Setup on your server is paid in full before work begins. We do not automatically debit a card or account.

5.4. We send a service report on Telegram each month and a completion report after a one-time setup and handover. Please tell us promptly about incomplete or defective work. For business orders, the reported work is treated as accepted unless you give specific objections within five business days. This does not waive a consumer's rights or any claim that applicable law does not allow to be waived.

6. If CI is not faster

6.1. If the median full-run time after connection is not lower than the baseline measured before connection, you can request a refund of the first managed-service month or the one-time setup payment.

6.2. Both measurements must use the same instructions, repositories, workflows and set of jobs. Full-run time runs from the workflow start to completion of its final job. Your agent supplies both reports so we can compare them.

6.3. Send your request and both reports within 14 calendar days after connection. We refund the eligible first payment within ten business days, or sooner if applicable law requires. The contract then ends.

6.4. Website run times describe example projects. Your measurement establishes your result. This commercial refund is additional to statutory rights and does not set a deadline for claims about defective service or consumer withdrawal.

7. Consumer withdrawal

7.1. If you are a consumer in the United Kingdom or European Union, you normally have the right to cancel a distance service contract without a reason during the 14 calendar days after the day the contract is made. Any longer period or additional right required by applicable law remains available. Consumers elsewhere retain the cancellation rights their applicable law provides.

7.2. Send a clear cancellation statement on Telegram @progonci or by post to the address in section 15 before the deadline. You may use the form in section 16, but you do not have to. Tell us your name and which order you are cancelling. We acknowledge a cancellation received on Telegram in the same chat.

7.3. If you want work to start during the withdrawal period, we ask for your separate express request in writing. You can decline and wait until that period ends. Payment or acceptance of these terms alone is not an early-start request.

7.4. If you requested an early start and then withdraw, you pay only the proportionate amount lawfully due for services actually supplied before your cancellation. We explain that calculation before you make the request. You bear no charge where the law excludes it because we did not obtain the required request or provide the required information.

7.5. For a fully performed service, the withdrawal right ends only when the law's conditions are met, including your prior express request and acknowledgement that full performance ends that right. Connecting a managed server does not fully perform the continuing managed service or support contract. We do not treat it as a completed digital download.

7.6. We reimburse payments due after withdrawal without undue delay and within 14 calendar days after receiving your notice. We use the original payment method unless you expressly agree otherwise, and charge no refund fee. A lawful proportionate amount under clause 7.4 may be deducted. If a legal restriction affects a refund, we notify you and pursue a lawful route without treating that restriction as a waiver of your entitlement.

8. Your project and permitted use

8.1. You must have authority to run the repositories and share the required access. Keep your own copy of source code and data you need. Use the agreed access channel and provide only the permissions and secrets needed for the work.

8.2. Do not use the runner for unlawful activity, unauthorised access, malware, or work outside the agreed service. Do not send export-controlled material, production personal datasets, regulated sensitive information or government-restricted data unless we have confirmed that we can lawfully handle it under an appropriate written arrangement.

8.3. Both parties must comply with laws that apply to them, including sanctions, export controls and data protection. We assess the specific country, parties, payment route, software, data and end use before access or payment. If we cannot lawfully provide the requested service, we decline it. We do not guarantee availability in every country.

9. Access, confidentiality and personal data

9.1. For the managed service, our administrative access uses SSH keys. The service server is dedicated to your workloads. We do not routinely inspect the contents of your code, secrets or data. Diagnostic inspection takes place at your request and only to the extent needed to investigate the issue.

9.2. Runner working files, local logs and caches are stored on the service server. GitHub and any services your workflows call process information under their own arrangements. The order identifies our hosting and administrative access locations before connection. A server's location alone does not determine where administrators can access data.

9.3. Each party keeps the other's non-public code, infrastructure details and business information confidential. Disclosure is limited to people who need it for the agreed service and are bound by confidentiality, or to disclosures required by law. Personal-data obligations and any agreed transfer safeguards continue to apply.

9.4. Before we process personal data on your behalf, we agree the required processing instructions, security measures, subprocessors, retention and assistance obligations. Any international transfer must have an applicable lawful basis and safeguards before access begins, including during a free trial. These terms alone are not a data processing agreement or a completed international transfer assessment.

9.5. Use synthetic test data where possible. Tell us before connection if repository metadata, fixtures, logs or other materials contain personal data. We pause the proposed transfer until the necessary arrangements are in place.

9.6. On your own server, you grant and revoke our access. At the end of the work or support, we remove the access credentials we hold. The privacy notice explains our handling of website and contact information.

10. Service problems and remedies

10.1. We perform the service with reasonable care and skill and correct our setup errors without using your included change hours. Tell us what failed and provide the information reasonably needed to investigate it.

10.2. If a managed server is unavailable through our fault for more than 24 consecutive hours, we reduce that month's fee in proportion to the downtime. This credit does not replace a consumer's statutory remedies.

10.3. For consumers, applicable rights to proper performance, correction, price reduction, termination or a refund remain available. Where digital-service law applies, its conformity and remedy rules also apply. The performance-refund procedure in section 6 is not your only remedy.

10.4. GitHub outages, your hosting provider, or changes you make to code and workflows can affect CI. We are not responsible to the extent a problem is caused by those matters and not by our breach. This does not remove our agreed support duties or responsibility that the law places on us.

11. Liability

11.1. Nothing in this contract excludes or limits liability for fraud, deliberate misconduct, death or personal injury caused by negligence, or any liability that applicable law does not allow to be excluded or limited.

11.2. For business customers only, and subject to clause 11.1 and any mandatory law, our total liability arising from an order is limited to the fee paid for the last month of the affected recurring service, or the setup price for a one-time setup order. Within those limits, we exclude liability for lost profits to the extent the law permits. Agreed refunds and fee reductions remain payable and are not reduced by this cap.

11.3. Clause 11.2 does not apply to consumers. We remain responsible for loss or damage caused by our breach to the extent required by applicable law.

12. Term, cancellation and changes

12.1. Managed service and optional support are agreed and paid month by month. Tell us at least ten calendar days before the end of the current paid month if you do not want another month. That notice period does not require you to buy a renewal you have not accepted.

12.2. Either party may end the contract for the other's material breach if it remains uncorrected after reasonable written notice and an opportunity to put it right. We may suspend the affected work immediately where necessary to address unlawful use, a serious security incident or a legal prohibition. We explain the reason and next steps where legally permitted, limit suspension to what is necessary, and refund unearned advance payments where required. We do not retain payment for work we cannot lawfully provide merely because it was prepaid.

12.3. Setup on your server ends after connection, verification and configuration handover unless support is ordered. Changes to future prices or terms require your agreement before the affected order. They do not change an accepted fixed scope or paid period.

13. Ending access and returning data

13.1. When managed service ends, we disconnect its runners, clear the server disk and notify you within three business days. We first allow any return of data required by the agreed processing terms or mandatory consumer rights. If those duties require a different deletion date, we explain it and limit retention to that purpose.

13.2. Ask for any configuration or customer-created content you are entitled to retrieve before deletion. Where consumer law requires retrieval, we provide it without a fee, within a reasonable time and in a commonly used machine-readable format. We retain accounting or legal records only as required for their separate lawful purpose. You should revoke runner tokens, credentials and access that you control.

14. Complaints and applicable law

14.1. Send service complaints on Telegram @progonci, identifying your order and the remedy you seek. We respond within ten business days. You do not have to complete this complaint process before exercising a statutory withdrawal right, seeking urgent relief or using a remedy the law gives you.

14.2. Applicable law determines the governing law and competent courts unless a valid written order expressly agrees otherwise. A choice in a business order does not remove mandatory protections. If you are a consumer, you retain any protection and right to use your local courts that the law of your country gives you.

15. Provider and contact details

16. Optional consumer withdrawal form

Use this form only if you wish to withdraw. You can send it on Telegram or by post. You may also use any other clear statement.

To: Individual entrepreneur Pavel Sergeevich Shumilin, Apartment 51, 10 Smolenskaya Street, Moscow 121099, Russia. Telegram: @progonci.

I give notice that I withdraw from my contract for the following service:

Service and order number:

Contract date:

Consumer's name:

Consumer's address:

Date:

Signature, only if sent on paper: