Scroll the table sideways to compare plans.
| Capability | CommunityFree testing plan | ProSingle-seat subscription | TeamPer-seat subscription, 1 to 50 seats | Detail |
|---|---|---|---|---|
| Getting started | ||||
| VS Code extension and setup | Included | Included | Included | Install the extension, sign in, and use the setup and account surfaces on either plan. Everything below also requires the extension to be enabled. |
| ERP environment profiles | Included | Included | Included | Define, switch, and diagnose connections to multiple Epicor environments. The mode configured on a profile constrains what either plan can do against it. |
| Seat and device allocation | 1 seat1 active device | 1 seat1 active device | 1 to 50 named seats1 active device per seat | Community is a single testing seat limited to one active device. New Pro subscriptions include one seat with one active device; existing multi-seat Pro subscriptions keep the seats they already hold. Team allocates one active device per named seat and scales from 1 to 50 seats. |
| Explore and understand | ||||
| ERP Explorer domain tree | Read-only | Read + write | Read + write | Both plans browse, expand, and search the enabled domain tree. Community stops at reads; Pro also runs the mutating commands surfaced from the same nodes. |
| erp:// documents and dedicated forms | Read-only | Read + write | Read + write | Open any artifact as an erp:// document or in its dedicated form. Community renders and inspects the artifact; saving it back to the server is a Pro workflow. |
| BAQ execution and analysis | Included | Included | Included | Read definitions, inspect tables, joins, and column metadata, analyze a query, and execute it with bounded results on either plan. Persisting changes to the BAQ design is a separate Pro authoring workflow. |
| Logs, server files, and FileStore viewing | Included | Included | Included | Read server logs, browse server files and FileStore entries, and export a copy to the local machine. Reads and local exports need only an enabled extension. |
| Report and document previews | Included | Included | Included | Render report and document previews and save them locally on either plan. Operations that persist the rendered output back into the environment remain Pro-only. |
| AI and automation | ||||
| MCP and VS Code language-model tools | Read-only tools | Read + write tools | Read + write tools | Read-only MCP, language-model, resource, and UI-to-tool operations run on Community. Tools that mutate ERP state are refused without the Pro consumer-workflow entitlement. |
| Packaged golden samples and tool catalog | Included | Included | Included | The tool catalog and packaged golden sample payloads ship with the extension, so agents can discover schemas and shapes without contacting a server. |
| AI-assisted read workflows | Included | Included | Included | Have an agent browse the tree, read artifacts, correlate logs, and draft a change plan. Every step stays inside the read-only tool surface. |
| Persistent AI-driven changes | Pro-only | Included | Included | An agent action that writes to the ERP is a consumer workflow. It requires Pro plus a writable environment, agent-write policy, an explicit confirmation gate, and an audit record. |
| Pre-approved chat writes and approval management | Pro-only | Included | Included | Grant a chat session or the whole VS Code session standing write approval, then review and revoke those grants. Community has no write path to pre-approve. |
| Authoring and delivery | ||||
| BAQ, BPM, and EFx editing | Inspect and plan | Full workflow | Full workflow | Community opens designers, directives, and function code to read the logic and plan an edit. Graph saves, code saves, and deletes require Pro. |
| AppStudio and Kinetic iteration | Read-only | Full workflow | Full workflow | Read layers, components, events, and bindings on either plan. Editing a layer and publishing it back to the environment is a Pro authoring workflow. |
| Preview Browser runtime inspection | Included | Included | Included | Attach the Preview Browser to a live Kinetic session and inspect the running component tree, data views, and current runtime values. |
| Preview Browser runtime scalar changes | Pro-only | Included | Included | Setting a value in a live session mutates runtime state, so it is treated as a consumer workflow rather than an inspection. |
| Greenfield report preflight | Validate and plan | Included | Included | Validate a report specification, resolve its data sources, and review the compilation plan before anything is created on the server. |
| Greenfield report execution | Pro-only | Included | Included | Creating the query, layout, and report definition records in the environment is a persistent mutation and needs the Pro entitlement. |
| Native artifact import and round trips | Pro-only | Included | Included | Importing a native export, or exporting and re-importing an artifact to move it between environments, writes server records. Community can export locally but not import. |
| Kinetic solution packaging | Pro-only | Included | Included | Assembling and installing a solution package changes environment content, so packaging workflows sit behind the Pro entitlement. |
| Structured SSRS authoring | Pro-only | Included | Included | Editing report structure, datasets, and styles and saving the result back to the report server is an authoring workflow. Community can still read and preview reports. |
| Classic client artifact authoring | Pro-only | Included | Included | Creating and saving classic client customizations and their related artifacts requires Pro. Community reads the same artifacts for reference. |
| Administration and governance | ||||
| UD Codes, system tasks, and EFx administration | Read-only | Read + write | Read + write | List and inspect UD Code sets, scheduled system tasks, and function libraries on Community. Creating, editing, or deleting any of them is a Pro administration write. |
| Menu security changesets | Review only | Apply changes | Apply changes | Community reads menu and security assignments to review the current state. Applying a security changeset is a Pro administration workflow with its own confirmation gate. |
| Read-only, writable, and live environment modes | Included | Included | Included | Both plans honor the mode configured on each profile. Community behaves as read-only regardless of mode; Pro writes only where a profile is writable. |
| Confirmation gates and before-image conflict checks | Write refused | Guarded writes | Guarded writes | Community refuses persistent mutations at the entitlement boundary. Pro then applies the write pipeline: a fresh before-image, conflict detection, explicit confirmation, a single-use gate, readback, and audit. |
| Audit log and local activity history | Redacted view | Included | Included | Redacted audit and local activity history is readable on both plans. Pro additionally generates audit entries for the write operations it performs. |
| Corporate proxy and certificate diagnostics | Included | Included | Included | Proxy detection, certificate trust inspection, and connection diagnostics are available on either plan so a connection can be validated before purchase. |
| Named seats managed in the customer portal | Not included | Single seat | Included | Team owners and admins assign, reassign, and revoke named seats in the EpiDev customer portal. Community and Pro are single-seat plans with no seats to manage. |
| Centralized billing under the organization owner | Not billed | Individual | Included | Team puts every seat on one subscription billed to the organization owner, who can add or remove seats through a Stripe-hosted review before anything is charged. |
| Basic seat analytics | Not included | Not included | Included | Team owners and admins see how many purchased seats are assigned, how many holders have activated the extension, and how many devices hold a valid activation. Counts reflect activations, not online presence. |
| SAML/SSO, managed extension policies, and enterprise connectors | Enterprise | Enterprise | Enterprise | Single sign-on, centrally managed extension policies, and enterprise connectors are Enterprise capabilities. Team does not include them. |
| Commercial | ||||
| Price | $0No credit card required | $30 per user, per month$324 per user, per year | $40 per seat, per month$432 per seat, per year | Community is free access for testing the software. Pro is priced per user for an individual Epicor developer using EpiDev every week. Team is priced per named seat for a whole team on one subscription. |
| Billing cadence | Not billed | Monthly or annual | Monthly or annual | Annual Pro is $324 per user per year, equivalent to $27 per user per month. Annual Team is $432 per seat per year, equivalent to $36 per seat per month. Both annual rates are 10 percent lower than paying monthly. |
| Seats | 1 testing seat | 1 seat | 1 to 50 named seats | Community has a maximum quantity of one seat. New Pro subscriptions are exactly one seat; existing multi-seat Pro subscriptions keep their current capacity and move to Team to add more. Team scales from 1 to 50 named seats on one subscription; larger teams are Enterprise. |
| Active devices | 1 active device | 1 per paid seat | 1 per seat | Each plan allows one active device per seat, so Community is a single machine at a time, Pro is one machine, and Team grows with the number of named seats. |
| Support | SupportedNo response-time SLA | SupportedResponse within 3 business days | SupportedResponse within 3 business days | Every edition includes product support. Community support has no guaranteed response time; Pro and Team support target a response within three business days. |
| Updates | Regular updates | Regular updates | Regular updates | Community, Pro, and Team all receive regular extension updates. |
| Builders program benefits | Not included | Not included | Not included | Preview features, daily builds, and Discord access belong to the Builders plan, which is unchanged. Team does not include them. |