Install Magento modules
the modern way,
in one require.
Run composer require once, then let updates find you. Manage every licence you own from one dashboard. Free and paid modules live in the same catalog, so the right tool is one search away.
# 1. add the registry once composer config repositories.packagento composer https://packagento.com/ # 2. require any licensed package composer require vendor/module:^1.0
Buying a module takes four steps
Find it
Search the registry, filter by category, version, or vendor. Quality signals (code style, static analysis, security audit) are visible inline on every listing so a senior dev can sanity-check before installing.
Buy it
Checkout is Stripe-powered. Card, SEPA, Apple Pay, Google Pay, plus other regional methods where available.
Authorise it
Assign the license to your project and paste your project token into auth.json. Tokens scope to a single project so different stores never share credentials.
Install it
Run composer require vendor/module, then bin/magento setup:upgrade. Same flow as any Packagist package.
Why merchants pick Packagento
One auth token, every licence
Per-project tokens authenticate every package you have licensed. No second portal for vendor licence keys, no parallel credential chain to chase down at install time.
Updates that find you
A one-line email lands when a vendor ships a new release, linking to changelog and quality results. composer update handles the install.
Free and paid, one catalog
No price floor walls off the free Magento ecosystem. The right tool for the job is the right tool, regardless of price.
Quality you can read
Every release shows pass / fail for code style, static analysis, security audit, and copy-paste detection. Filter the registry by quality before you click into a listing.
Money-back on first purchase
New marketplace, real risk. Your first paid module is refundable within 14 days, no questions asked. Subsequent purchases follow the full refund policy.
Composer-native, end to end
No zip uploaders, no admin wizards, no SFTP. If your install flow is composer require already, Packagento drops in without changing anything.
See the source of what you have bought
Every package archive Packagento serves is built from the vendor's tagged source. When you license a paid module, Composer extracts the files into vendor/vendor/package and you can read every line. Patch with cweagans/composer-patches, fork privately, audit before you deploy.
- Before you buy: the package detail page shows the vendor's linked source repository, the composer type, and the declared licence string. Encoded or compiled drops are rare; if you need certainty, the vendor contact is on the same page.
- After you license: read, patch, fork. Local patches do not affect other licensees. The marketplace is not in the way.
- Vendors who choose to ship obfuscated code can, but they have to declare it. Buyers see the signals before checkout.
Buy from many vendors, pay once
Every Packagento order is multi-vendor capable, even when your cart is from a single seller. One card, one Place Order click, and a per-vendor breakdown lists every recipient with the amount routed to them.
- Cards processed by Stripe; SCA-ready for European cards, accepts SEPA, Apple Pay, Google Pay where available.
- Each vendor receives their share directly via Stripe Connect. The marketplace does not sit on the money between buyer and vendor.
- Invoice with the per-vendor split appears on the order receipt; finance teams can reconcile each charge against the vendor it paid.
Common questions
What if a module breaks my install?
Raise a refund through your Licenses page within the refund window. Packagento reviews, mediates with the vendor, and either issues the refund or routes a fix. The full flow is in refunds and disputes.
Who do I contact for support?
The vendor handles bug reports and feature requests for their module; their contact lives on the package detail page. Packagento handles billing, licence, account, and refund tickets directly.
Can I move a licence to a different project?
Yes. Re-pin the licence to the project that needs it; the previous project loses install access on its next composer update. See project package activation for the mechanic.
What about renewals on subscription modules?
Annual renewal on the card on file; basic vendor support is included for the term. Cancellation stops the next renewal but leaves the module functional. See subscription renewals.
Find your next module.
Browse the curated registry, set up Composer in four steps, and install your first module with one require line.