ever-demand
Ever Demand is an open-source, TypeScript-based e-commerce and on-demand platform supporting multi-vendor marketplaces, real-time order management, and mobile apps for customers, merchants, and drivers. Licensed under AGPL-3.0, it provides headless commerce APIs (GraphQL, REST, WebSocket) with MongoDB backend and Angular/Ionic frontends.
Key facts
Objective fields from the source. Values we can't verify are shown as “Unknown” rather than guessed.
| Field | Value |
|---|---|
| Repository | ever-co/ever-demand |
| Owner | ever-co |
| Primary language | TypeScript |
| License | AGPL-3.0 — OSI-approved |
| Stars | 1.8k |
| Forks | 475 |
| Open issues | 71 |
| Latest release | Unknown |
| Last updated | 2026-07-05 |
| Source | https://github.com/ever-co/ever-demand |
What ever-demand is
Full-stack TypeScript platform built on NestJS backend with GraphQL/REST/WebSocket APIs, MongoDB (with planned TypeORM/Prisma support for SQL DBs), Ionic mobile apps, and Angular admin/storefront UIs. Uses RxJS for reactivity and Socket.io for real-time features.
Get the ever-demand source
Clone the repository and explore it locally.
git clone https://github.com/ever-co/ever-demand.gitcd ever-demand# follow the project's README for install & configurationNeed it deployed, integrated, or customized instead? DEV.co ships production installs.
Best use cases
Implementation considerations
- AGPL-3.0 license requires source disclosure to end users; conduct IP/legal review before deployment, especially for SaaS or proprietary products.
- Alpha status with WIP database support (TypeORM/Prisma), plugins, permissions, and tax calculations; assume feature gaps and need for custom development.
- Full-stack TypeScript expertise required; team must be comfortable with NestJS, Angular, Ionic, RxJS, MongoDB, and monorepo patterns (Lerna).
- Demo infrastructure offline; plan for self-hosted setup using provided Docker/PM2 guidance; Kubernetes migration ongoing (status unclear).
- 71 open issues and no formal release cadence; evaluate community responsiveness and roadmap alignment before committing to critical features.
When to avoid it — and what to weigh
- Production maturity required immediately — Project is marked alpha with frequent changes. No official releases; last push July 2026 but no versioned releases listed. Expect instability and breaking changes.
- Strict proprietary licensing needs — AGPL-3.0 requires derivative works to be open-sourced and disclose source to users. Incompatible with closed-source SaaS or products that cannot expose modifications.
- Legacy SQL database requirement — Currently MongoDB-focused; SQL support (MySQL, PostgreSQL, etc.) is WIP via TypeORM/Prisma. Existing schema and migrations may not be production-ready.
- Minimal operational/support infrastructure — No SLA, commercial support, or enterprise deployment guides documented. Community-driven; demos currently offline during Kubernetes migration.
License & commercial use
AGPL-3.0 (GNU Affero General Public License v3.0). Strong copyleft: any modifications or derivative works must be open-sourced, and users must have access to source code. Incompatible with proprietary/closed-source business models unless entire product is open-source.
AGPL-3.0 permits commercial use, but with mandatory source disclosure. Using this as-is for a SaaS or proprietary platform requires either: (1) open-sourcing all modifications, (2) licensing commercial exception from Ever Co (not mentioned in data), or (3) redesigning to avoid distribution of derivatives. Requires legal review before production deployment.
DEV.co evaluation signals
Editorial assessment — not user reviews. Directional, with an explicit confidence level.
| Signal | Assessment |
|---|---|
| Maintenance | Active |
| Documentation | Adequate |
| License clarity | Clear |
| Deployment complexity | High |
| DEV.co fit | Good |
| Assessment confidence | High |
No security audit, vulnerability disclosure policy, or hardening guidance provided in data. AGPL-3.0 source availability aids transparency but does not guarantee secure coding. Alpha status suggests unproven security testing. Payment processing (Stripe) integration must be validated. Assess authentication, authorization, data encryption, and network security before production use. Conduct threat modeling and penetration testing independently.
Alternatives to consider
Medusa
Open-source headless commerce (MIT license), production-ready with versioned releases, strong documentation, and modular plugin ecosystem. MIT is more permissive than AGPL-3.0.
Saleor (GraphQL Commerce)
Open-source e-commerce platform (BSD 3-Clause), mature with versioned releases, multi-vendor support, and hosted/self-hosted options. More established than Ever Demand alpha.
Shopware
Enterprise-grade headless commerce (AGPL-3.0 community + commercial editions), mature feature set, dedicated support, and Kubernetes-ready deployments. Steeper learning curve but production-proven.
Build on ever-demand with DEV.co software developers
Ever Demand offers powerful headless commerce APIs and real-time capabilities, but requires careful licensing review for commercial use. Consult our team on AGPL-3.0 implications, deployment strategy, and whether a production-ready alternative better fits your timeline.
Talk to DEV.coRelated on DEV.co
Explore the category and the services that help you build with it.
ever-demand FAQ
Can we use Ever Demand for a SaaS product?
What databases does Ever Demand support?
Is Ever Demand production-ready?
What support is available?
Work with a software development agency
From first prototype to production, DEV.co delivers software development services around tools like ever-demand. Our software development agency staffs experienced software developers and web developers for custom software development, web development, integrations, and ongoing support across open-source ecommerce and beyond.
Evaluate Ever Demand for Your Project
Ever Demand offers powerful headless commerce APIs and real-time capabilities, but requires careful licensing review for commercial use. Consult our team on AGPL-3.0 implications, deployment strategy, and whether a production-ready alternative better fits your timeline.