Virto Commerce is an open-source, .NET-based, headless, API-first commerce platform — built B2B-first, ready for B2C, marketplace, DTC, and composable scenarios. This page is the entry point for developers: spin it up, understand what you're building, and ship.
👉 Virto Commerce B2B Marketplace
👉 Explore Virto’s Open-Source .NET ecommerce platform
👉 Learn more about B2B features of Virto’s platform
👉 Browse careers at Virto Commerce
As a Microsoft Gold Partner, Virto serves over 100 companies worldwide and has offices in five countries, including the Americas and Europe. Leveraging our open-source ecommerce platform, hosted solution and full-service offering, our clients strategically use ecommerce to build stronger customer relationships and rapidly increase global online sales. Virto Commerce’s flagship product, the ecommerce cloud-based, open-source, .NET platform, is the only B2B-first headless digital commerce solution that is specifically designed to adapt to ever-changing complex scenarios common in the B2B market.
At Virto Commerce, we pride ourselves on being proactive technology innovators deeply dedicated to creating flexible, agile commerce software solutions that improve business and accelerate digital adoption. All this requires a special mindset and a lot of collaborative effort to make complex things simple. We believe in the uniting power of technology, teamwork and spirit, and we take personal responsibility for every project we undertake.
👨💻 Download and Read - Virto Architectural Guidelines
👨💻 Ask Virto Oz – Your Conversational AI Copilot
Use start-local to bring up the full stack (platform, frontend, database, Redis, Elasticsearch, Kibana) on your machine with one PowerShell command.
$installSCript = Invoke-WebRequest -Uri "https://raw.githubusercontent.com/VirtoCommerce/start-local/dev/VirtoLocal_create_local_files.ps1" -UseBasicParsing; Set-Content -Path ".\VirtoLocal_create_local_files.ps1" -Value $installSCript.Content; .\VirtoLocal_create_local_files.ps1👨💻 What are the skills required for Virto Commerce Developer?
👨💻 Virto Commerce Dev Training Program
👨💻 Virto Commerce Documentation
Virto Commerce is designed to be extended through custom modules, not by modifying the platform source. The Extensibility Framework lets you add entities, override services, extend APIs, and add admin UI — all without forking.
dotnet new install VirtoCommerce.Module.Template
dotnet new vc-module --ModuleName MyModule --Author "Me" --CompanyName MyCompanyBuild with vc-build, install the resulting .zip into your local platform via Modules → Advanced → Install from file, and iterate.
vc-build compressA Virto solution is composed, not forked:
| Layer | What you do | Repo strategy |
|---|---|---|
| Platform | Use Virto's official Docker images or binary package | ❌ No fork |
| Custom modules | One repo per module, generated from the template | ✅ Your repos |
| Frontend | Brand and extend the storefront | ✅ Fork vc-frontend, track upstream |
| Deployment | Compose the environment from independent images | ✅ Virto Cloud, Azure, AWS, on-prem |
This separation enables seamless Virto upgrades — your customisations stay yours, and the platform stays current.
Virto Commerce ships as modules — independently versioned, independently deployable units. Modules combine into bundles you can pick from based on how you want to balance stability and speed.
| Release Strategy | What it is | Use it for |
|---|---|---|
| Stable | Quarterly release; passed full regression, E2E, and load testing | Production, new solution development (default in vc-build) |
| Hotfix | Bug fixes for the two most recent stable releases | Maintenance updates between stable cuts |
| Edge | Latest features as they land — minimal risk, maximum freshness | Early access to new capabilities, prototyping |
Tip
Open any deck via the links above, or clone the repo and open the index.html files directly in your browser. Add a feature to your backlog, then navigate to the Backlog screen and click Copy as Markdown.
| Month | Live deck | Source notes |
|---|---|---|
| April 2026 | 📊 View deck | Notes |
| March 2026 | 📊 View deck | Notes |
| February 2026 | 📊 View deck | Notes |
| January 2026 | 📊 View deck | Notes |
We welcome contributions — code, docs, bug reports, feature ideas. The fastest path:
- Fork the relevant repo (e.g., vc-platform, vc-module-catalog, vc-frontend).
- Branch from
dev— notmaster. Create a topic branch:git checkout -b feature/short-description. - Commit and push to your fork, then open a pull request against the upstream
devbranch. - Sign the CLA when prompted on your first PR — required for all contributors.
- Each PR automatically produces an Alpha release so you can test your changes against a real build before merge.
- 🐛 Browse open issues — issues labelled good first issue are best for newcomers.
- 💡 For larger ideas, open a discussion or an issue before coding so maintainers can shape the approach.
- 📝 Documentation fixes (typos, broken links, clarifications) are always welcome and the easiest way to get familiar with the workflow.
