Composer only allows one key per repository. RexSync lets you use multiple keys for any PHP project - Magento 2, TYPO3, WordPress, Symfony - syncing everything to your own private package source.
Standard Composer Limitation:
Only one key per repository domain is allowed. Multiple keys cannot be used together.
Only one key can be active at a time
Modern PHP projects rely on dozens of repositories with different authentication requirements. Composer's one-key-per-domain limitation creates a nightmare for developers and agencies working with multiple clients.
Different parties with their own keys for the same repositories
Legacy projects with accounts from previous owners
Builds fail due to missing keys or blocked bots
Modern PHP projects (especially Magento 2) typically use 10-30 different repositories from various vendors and frameworks.
Each repository requires its own authentication credentials, often tied to specific accounts or licenses.
Composer only supports one authentication key per domain, making multi-client work impossible.
Build pipelines break when they can't access all required repositories with the right credentials.
A comprehensive solution that transforms your Composer workflow from complex to simple.
RexSync continuously monitors your configured repositories and automatically syncs all available packages to your auto-generated Composer Satis repository.
Regular updates on your schedule
Sync on demand when needed
All packages in unified repository
autogenerated-123.composer.rexsync.com
Your keys stay encrypted and secure in our infrastructure
Parallel downloads and intelligent caching for maximum speed
99.9% uptime guarantee with redundant infrastructure
Perfect integration with your deployment pipelines
Your packages are available even when the original repositories are down
Composer limits you to 1 key per repository. RexSync lets you use unlimited keys.
The limitation we solve
Standard Composer Limitation
Only one key per repository domain is allowed. Other keys are blocked.
RexSync supports every Composer repository that requires authentication. Primarily focused on Magento 2, but fully compatible with TYPO3, WordPress, Symfony, Laravel, and any PHP project using Composer.
RexSync supports any Composer repository that requires authentication - from Magento and TYPO3 to Symfony, Laravel, WordPress and beyond. If you don't see your specific repository listed, you can still add it to your RexSync setup.
Add your composer repositories and multiple keys via our interface
We fetch all packages and serve them from your auto-generated Composer repository
Use your repository URL with Packeton, Satis or any Composer-based project
Experience how RexSync handles multiple repositories and authentication keys in this interactive demo.
Add the repositories you want to sync and their authentication keys.
https://repo.magento.com
https://repo.amasty.com
Host your packages locally on your own server. Zero downtime, even from us.
Download and host all your packages on your own infrastructure. Complete independence from any external service, including RexSync itself.
Your builds work even when the internet is down
All packages stored on your own servers and infrastructure
Local network speeds for all package downloads
Keep sensitive packages behind your own firewall
Join our early access program and get notified when self-hosted RexSync becomes available.
Join our waitlist to get early access and be the first to know about pricing when we launch.
Perfect for trying out RexSync
For growing teams and agencies
For large agencies and enterprises
All plans include:
Be among the first to experience RexSync when we launch in Winter 2025
Get 50% off your first year when we launch
Be among the first to access RexSync before public launch
Your feedback will directly influence our feature roadmap
Get behind-the-scenes updates and beta access
Join our exclusive waitlist and get priority access, early-bird pricing, and be part of shaping the future of Composer package management.
Be the first to know when RexSync launches