Merchant & operations
Understand Agovena
Learn what Agovena is, which commerce problems it covers, and where Modules, Extensions and Themes fit.
On this page
Agovena is an open-source, self-hosted commerce platform for teams that want to run their own store and keep control of the infrastructure behind it. It provides a shared foundation for products, customers, checkout, orders, payments and invoices, then lets you add the capabilities that match your business.
You can use Agovena for a focused physical product shop, digital delivery, subscriptions, hosting and provisioning, domain sales, event tickets, or a combination of these. You do not need to choose a permanent store type before you begin. Use Core capabilities for platform commerce behavior, connect an external service through an Extension, and use a Theme to shape the storefront and Admin experience.
What Agovena gives you
- A commerce foundation: Products, customers, carts, checkout, orders, payments and invoices share one application model.
- Core commerce: Availability, Physical and Recurring are built-in Core capabilities. Modules can add optional areas such as digital delivery, domains and events.
- Provider connections: Extensions keep payment, carrier, provisioning and domain-provider behavior at an explicit integration boundary.
- Your infrastructure: Run the application on a Linux server or with Docker Compose, manage your data, and choose your operational tools.
- A documented API: Integrate customer-facing flows with scoped tokens and a versioned Storefront API.
- A changeable presentation: Themes own storefront and Admin presentation without taking ownership of business rules.
Common starting points
A merchant can start with the requirements and installation guide, then configure the store and add a first product. A developer can read the architecture guide, browse the API overview, or learn how to build a Module or Extension. The marketplace shows the packages that are currently documented for the platform.
Agovena is early-stage software. Read the guides, inspect the source, test the flow you need in a separate environment, and make an operational plan for backups, updates, queues and security before accepting live orders.