Ship from Git.
Get paid in 14 days.
License on your terms.
Push a release tag, we serve it the same day. Sales settle to your Stripe Connect account in roughly two weeks. License events fire to your own endpoint, so your existing licence server stays in charge of issuing, refreshing, and revoking keys.
# 1. tag a release in your repo git tag v1.4.0 git push origin v1.4.0 # 2. Packagento ingests, runs QA, # and serves buyers within minutes
Onboarding in four steps
Apply as a vendor
Tell us who you are and what you intend to publish. Most applications clear within a few business days.
Connect your Git provider
GitHub or GitLab. Packagento installs an app on your selected repositories and watches for tag pushes.
Add your first package
Pick the repo, confirm the composer name, choose a pricing model. Push a tag and the release runs through QA on its way to the registry.
Connect Stripe Connect
One-time onboarding with Stripe directly. Payouts start landing the next time you make a sale.
Vendor economics at a glance
- Commission
- 20%
- Payouts in
- ~14 days
- Stripe coverage
- 46 countries
- Price floor
- None
Your public vendor profile
Every approved vendor gets a public profile page at packagento.com/{your-slug}. Buyers reach it from package detail pages and from the marketplace browse surface. The profile lists every package you publish, your display name, your support contact, and the external links you set (homepage, repository, documentation site). See the vendor public profile docs for what each field shows.
- Profile fields you control: display name, bio, homepage URL, support email, location, social links.
- Marketplace-derived fields: vendor since (your approval date), package count, total release count, quality average across your catalogue.
- Verified-vendor badge once your GitHub or GitLab org is linked back to the slug. Trust signal for new buyers.
What Packagento handles so you do not have to
Composer V2 distribution
Packages.json + p2 metadata + dist archives, cached behind a CDN, signed against your tagged source. You push tags; we serve them.
Auth and licence enforcement
HTTP-basic against project tokens, per-licence scoping, automatic revocation on refund. You see issued / refreshed / revoked events through the webhook contract; the policy is ours.
Payment infrastructure
SCA-ready Stripe checkout, multi-vendor cart splits, subscription renewal retries, refund reversals. Your share lands in your Stripe account; ours covers the rails.
Refund mediation
Buyers raise refunds against Packagento, not your inbox. We review with you in the loop and either issue or decline. Card-issuer chargebacks go through the same flow.
Quality pipeline
PHPCS, PHPStan, composer audit, and copy-paste detection run on every tag without you wiring CI. Results land on the release page; you act on what matters.
Missing-dependency detection
When a tag requires a package that is not yet on Packagento, the platform surfaces it on your dashboard with an Add shortcut before buyers see a broken install. See missing dependency detection.
Start selling on Packagento.
Apply, connect Git, add a package, connect Stripe. Most vendors are live and earning within a week.
Packagento vs Adobe Marketplace
Line by line, here is how the two platforms compare on the mechanics that actually affect your release cycle, your cash flow, and your geography.
| Adobe Marketplace | Packagento | |
|---|---|---|
| New release flow | Manual zip upload via Developer Portal, 30 MB cap | Push a tag to GitHub or GitLab |
| Payout method | PayPal only (excludes several countries) | Stripe Connect, ~46 countries |
| Payout cadence | 60 days after end of sales month | ~14 days via Stripe |
| Price minimum | $25 flat-fee, $10 subscription | No minimum |
| Listing title rules | Max 4 words, no brand name, no "Extension" | Your title, your call |
| Custom licensing | Adobe-managed flow only | Webhook events to your endpoint |
| Metapackages | Supported | Supported |
What makes the release flow different
Git tag ingestion
Connect GitHub or GitLab once. Push a semver tag. Packagento mirrors the repo, ingests the release, and serves buyers within minutes. No zip uploads, no portal flow per version, no 30 MB cap.
Stripe Connect payouts
Sales settle to your Stripe Connect account in roughly two weeks. Coverage spans about 46 countries. No PayPal account required, no 60-day wait.
Webhook-based licensing
We POST issued, refreshed, refunded, and revoked events to your HTTPS endpoint. Your licence server stays in charge: issue keys, gate features, expire access on your terms.
Quality checks on every release
PHPCS with the Magento2 ruleset, PHPStan with the type stubs, composer audit for advisories, and a copy-paste detector. Results land on the release page either way, no manual review per release.
Pricing flexibility
Free, paid one-time, or annual subscription with an optional higher first-year price. Metapackages for bundling related modules. No price floor: charge $5 or $500.
Activity feed for every event
Every release, sale, licence issuance, refund, and webhook delivery lands on a single timeline. Filter by package, event type, or date. The activity feed is the system of record, not the payout email.