Free is for proving the loop. Team is for standardizing it across working repos. Enterprise is for treating AI workflow as governed infrastructure.
Free
Great for proving the workflow before committing.
Try the full workflow in one repo — no credit card.
Team
For teams managing multiple repos with one shared model.
Standardize AI workflows across all your repos.
Enterprise
Full governance, compliance, and control at org scale.
Treat AI workflow as platform infrastructure.
The pricing model is operational, not cosmetic. The difference is how much surface area you can manage and how much governance NEPOPSX gives you around it.
Best for
Free
Proving the workflow in one repo
Team
Standardizing how a team works across repos
Enterprise
Running AI workflow as platform infrastructure
Scale
Free
2 services • 1 agent package • 1 workspace
Team
10 services • 5 agent packages • 5 workspaces
Enterprise
Unlimited services • Unlimited packages • Unlimited workspaces
Platform tooling
Free
CLI-based workflow and remote template delivery
Team
Dashboard, LLM-powered scan, package publishing, team sync
Enterprise
Everything in Team plus SSO, audit logs, webhooks, and on-prem options
Control model
Free
Local-first usage
Team
Shared workspace rollout
Enterprise
Org-wide governance and compliance
Support
Free
Community support
Team
Email support
Enterprise
Dedicated support
Rollout model
Free
Use one workspace to prove that the generated operating model is better than scattered markdown and one-off prompt tuning.
Team
Add dashboard access, scan, and team sync when multiple repos or multiple developers need the same behavior and standards.
Enterprise
Add SSO, audit, webhooks, and deployment controls when the platform team needs traceability and rollout guarantees.
The pricing story is straightforward once you separate agent quality from operational scale.
What am I actually paying more for on higher tiers?
Scale, coordination, and governance. Agent quality stays the same. Higher tiers unlock more services, more packages, more workspaces, team sync, dashboard tooling, and enterprise controls.
What counts as a service?
A distinct project or microservice described in workspace.yaml. Each service becomes part of the context model that NEPOPSX renders into your generated agent system.
Can I start free and keep the same workflow later?
Yes. The upgrade path is about capacity and platform surface, not a different operating model. You can start in one repo, then expand the same structure across the team.
Do I lose generated files if my license expires?
No. Existing generated files stay in the repo. License expiry stops future syncs and managed updates until you renew.
Does Team checkout work from this page?
Yes. If you are signed in and viewing the Team plan, the upgrade controls use the same billing flow already wired into the app, including eSewa and Khalti.