For agencies

Buy and sell modules
at agency scale,
across every store.

One Packagento org, every project pinned to its own token. Licence modules across every client store you run, and turn the modules you have already written for one client into a revenue stream selling to the merchants you do not manage.

Browse the registry Apply as a vendor

auth.json

# one token per project,
# rotatable without re-licensing
{
  "http-basic": {
    "packagento.com": {
      "username": "acme-prod",
      "password": "pk_live_..."
    }
  }
}

Per-project audit trails Org-level roles

Get started in any direction

Set up the org

Create your Packagento org and invite the team. Read about team and roles for the role and invite model.

Add a project per client store

One project per Magento install. Generate a token per project, save it in auth.json on that store, and start installing.

Apply as a vendor if you sell too

Connect a Git provider, add your first package, connect Stripe. The vendor-apply docs walk through review.

What an agency org looks like

Tokens: 1 per project
Roles: Org + project
Billing: One per org
Vendor payout: ~14 days

Why agencies pick Packagento

Project-pinned tokens

Every project gets its own API token. Different stores never share credentials. Rotate one token when a developer leaves, not every project.

Org roles, not shared logins

Invite junior developers to specific projects without granting billing access. Transfer ownership of a project to a client at the end of an engagement.

Discover across your portfolio

Search by category, vendor, Magento version, Hyva compatibility, or quality bar. Per-project activity feeds show every new release of every installed package.

Sell what you have already built

Most agencies have five to ten internal modules. Apply as a vendor, connect a Git repo, set a price. Tax patches, shipping rules, B2B account flows, ERP connectors. The other 50 merchants who need the same thing will find it.

Refunds without the back-and-forth

When a paid module breaks your install, raise a refund through Packagento. We mediate with the vendor, you watch the resolution land on the project activity feed. No three-way email thread between your client, your agency, and a vendor support inbox you have never written to.

Composer-native, agency-friendly

composer require fits the install flow you already have. No zip uploaders, no admin wizards, no SFTP to talk juniors through. Updates flow through CI the same way every other dependency does.

Activity feed per project

Each project has its own activity timeline: purchases, token changes, releases on installed packages, renewals, refund activity. Owners and admins see the workspace events; junior developers see only what touches their assigned projects. See the activity feed docs for the per-row format.

When a vendor releases a new tag on a module you have installed, the row lands on the project timeline within minutes.
Token rotations and member invites are audited automatically. No separate access-log to maintain.
Subscription renewal events surface here too, so finance does not have to chase the email trail.

One cart, multi-vendor payment splits

An agency cart often pulls modules from five different vendors. Packagento charges your card once and routes each vendor's share directly to them via Stripe Connect, with a per-vendor breakdown on the receipt. No more "place order on five vendor sites" sequences. No more reconciling five card charges against one engagement.

Finance gets one invoice with the per-vendor allocation already broken out.
Each vendor sees a charge from Packagento on their Stripe dashboard, with the buyer org name attached.
Multi-vendor refunds work the same way: the vendor whose module gets refunded eats the cost; the others are unaffected.