EdgeKits.dev Logo

Guías de RepoAccess

Guías de integración, una por proveedor

Qué hace cada proveedor por quien vende código, cómo el comprador indica su usuario de GitHub en el checkout y qué hace un reembolso con su acceso. Léelo antes de comprar.

Illustration of selling code with Gumroad: a Gumroad checkout with a GitHub username field, a sale, and a GitHub team invitation to a locked private repository, with a refund path looping back to access revoked.

Gumroad

Sell private GitHub repo access with Gumroad as merchant of record. RepoAccess Pro invites the buyer on payment and revokes on refund, on your own Worker.

Leer la página de integración →
Illustration of selling code with Lemon Squeezy: a Lemon Squeezy checkout, then a claim page where the buyer types a GitHub username, and a RepoAccess worker on Cloudflare that grants access to a private repository.

Lemon Squeezy

Sell private GitHub repo access with Lemon Squeezy as merchant of record. RepoAccess Pro invites the buyer on payment and revokes on refund, on your Worker.

Leer la página de integración →
Illustration of selling code with Paddle: a private GitHub repository, a Paddle merchant-of-record checkout with VAT handled and global payouts, and a RepoAccess worker that turns the payment into a GitHub team invitation.

Paddle

Sell private GitHub repo access with Paddle as merchant of record. RepoAccess Pro invites the buyer on payment and revokes on refund, on your own Worker.

Leer la página de integración →
Illustration of selling code from India with Razorpay: a Razorpay Payment Page with UPI, cards and a GitHub username field, a RepoAccess Pro worker on Cloudflare, and invitations to locked private GitHub repositories.

Razorpay

Sell private GitHub repo access from India with Razorpay. RepoAccess Pro invites the buyer on payment and revokes on refund or dispute, on your own Worker.

Leer la página de integración →
Illustration of selling code with Stripe: a successful Stripe payment flows into a RepoAccess worker, which grants access to a locked private GitHub repository, captioned secure, AGPL open source, refund and dispute handling.

Stripe

Sell private GitHub repo access with Stripe. The free AGPL core invites the buyer on payment and revokes on refund or dispute, on your own Worker.

Leer la página de integración →
Illustration of selling code with Telegram Stars: a bot chat on a phone with a verified GitHub username, a payment in Stars and an invitation sent, a Cloudflare Worker, a private GitHub repository with access granted, Stars sales charts, and access revoked on refund.

Telegram Stars

Sell private GitHub repo access for Telegram Stars from a bot. RepoAccess Pro checks the handle before payment and revokes on refund, on your own Worker.

Leer la página de integración →

Comparativas: las decisiones en torno a la entrega

Las decisiones que toma quien vende código además del proveedor de pagos: cómo habla el worker con GitHub y qué sustituye el acceso al repositorio. Cada una, lado a lado.

A fine-grained personal access token owned by a user account with a 366-day maximum, set against a GitHub App installation token minted from a private key that lasts one hour.

GitHub App vs Personal Access Token for Automated Private-Repo Access

GitHub App vs fine-grained PAT for automated private-repo access: token lifetime, ownership, rate limits, the calls a worker makes, and code for both.

Leer la comparativa →
A license key checked by a license server before an app runs, set beside GitHub repo access, where a team member clones the source and pulls each update.

License Key Server vs GitHub Repo Access: Which One a Code Seller Needs

License key server or GitHub repo access for selling code? What Keygen and provider keys do, why a check in source code fails, and which one fits.

Leer la comparativa →
← RepoAccess

Utilizamos cookies para analizar el tráfico del sitio y mejorar su experiencia. Al hacer clic en "Aceptar todo", acepta nuestro uso de seguimiento analítico.