At Medusa Commerce, we are introducing a new way of working with headless commerce. We are bridging the worlds of customizability and maintainability. Our open-source foundation and modular architecture allow for a fully flexible commerce engine, while our unique hosting and deployment model takes away the pain of server maintainability.
Medusa is an open-source headless commerce engine that provides the primitives necessary for others to build amazing digital commerce experiences. At the core we can handle orders, manage products, make sure payments are being processed correctly, and just as importantly we provide the foundation for integrating all parts of a business's commerce stack: e.g. accounting, marketing, analytics, fulfillment, etc. When you spin up a Medusa project you are ready to start selling, but the real power of Medusa comes when you begin extending and developing custom experiences - you can do so without worrying about breaking the critical parts of the system.
When working with Medusa you will only have to think about creating the features that move the needle for your organization or clients. Maintaining servers and infrastructure introduces a lot of overhead where developers spend time reading endless technical documentation from hosting providers, doing trial and error in the AWS console. Setting up an environment similar to what we will offer will take an experienced AWS developer around 2-3 weeks of just entering information, configuring environments to autoscale, and provisioning resources - if you are not experienced it may take several months as you will first have to familiarize yourself with all the different parts of an environment: e.g. security groups, database rules, IAM policies. Furthermore, you would have to setup up containerization, Node.js configuration, and an automatic deployment pipeline which may take additional weeks to optimize. On top of this comes the ongoing maintenance which smaller organizations may neglect, putting them at risk of security breaches, downtime, and the opportunity costs associated with not having better performing servers.
The key here might not be as much a question of how much effort we save customers but rather how early a customer can operate a headless stack. We make it possible to do it with just a single front-end developer - whereas other solutions will require you to have multiple developers and especially someone who is comfortable with working with infrastructure, which is typically the most expensive type of developer.