Developer EDI toolkit pricing, from free forever to $799 a year

No. Every plan includes all three. Pick a plan by how many leased seats you need, whether it is production, and whether your hosts can reach the internet. If you want to compare the products themselves, see all EDI products in a nutshell.

Paid plans cannot be stacked. You cannot hold Developer and Enterprise at the same time, or Developer and Perpetual, or Enterprise and Perpetual. Pick one paid plan; every plan already includes .NET, Native and Cloud (Perpetual excludes hosted Cloud).

Community can be combined with every plan. The only other combinations are:

• Enterprise + OEM - OEM is a rider and always requires an Enterprise plan
• Perpetual + Cloud-only - Perpetual covers .NET and Native, so Cloud-only is how you add the hosted API

Community is the trial and it never expires, so you can take as long as your integration takes. It is full-functionality apart from the daily quota and the ban on production use. To try ediFabric .NET, Native or Cloud before you sign up, use the demo serial key bd96a836feca45cb91c86ee65d281f52. It needs no account and has a limited quota.

The first 14 days after you create the Community subscription have unlimited operations, and the 250-a-day quota starts after that. If you need longer, ask through the support portal or at support@edifabric.com to extend the unlimited period.

Enterprise also has a 14-day trial, because unlimited leased seats and Cloud volume are the things Community cannot demonstrate. Developer has no separate trial - upgrade from Community by swapping the serial key.

In total. Community gives you one quota per account, and calls from .NET, Native and Cloud all count against the same 250 per day. That quota starts 14 days after you create the Community subscription; until then, operations are unlimited.

A single parse, generate, validate or acknowledge call, no matter how many transactions are in the payload. On Developer and Enterprise, operations on your own machines are unlimited and only Cloud calls are metered. Cloud requests are capped at 3 MB each.

A seat is a lease held by a single environment. One environment takes one seat, whatever its number of threads, developers or CPU cores. Community and Developer lease 3 seats, and Enterprise is unlimited.

Once you are at your limit and a new environment authenticates, the oldest lease is released and handed over to it. That rollover happens only if the oldest lease was taken on an earlier day, so moving between environments day to day needs no intervention from us.

If every seat was leased today there is nothing to roll over, so the new environment is refused until 24 hours have passed. Enterprise sidesteps this altogether, because offline tokens are not leased.

Enterprise and Perpetual only. Offline tokens make no license call once set. Self-service tokens last 30 days. On request, Enterprise can get a 1-year token and Perpetual a non-expiring token, so air-gapped hosts do not need a refresh job. Community and Developer validate online, but Developer caches the result, so a temporary outage or a long batch will not stop your job. During the Enterprise trial, offline tokens are available with a 1-day token lifetime, which changes to 30 days after purchase.

Ask for the Long-Lived Token Request Form through the support portal or at support@edifabric.com, and have it signed by someone authorized to bind your company. On Enterprise we issue a token after the 14-day trial has ended and payment has cleared. On Perpetual we issue it 14 days after purchase. Until then, use the self-service 30-day tokens. We aim to reply within one business day.

Long-lived tokens are issued only to registered legal entities, and only to professional email addresses on a domain your company owns. Public and disposable email addresses are declined. Long-lived tokens are non-refundable: once a token is issued, the money-back guarantee no longer applies.

A 1-year token runs to the end of your annual term plus 30 days, so a late renewal does not stop production. We send reminders before it expires and issue the next token once the renewal is paid. A Perpetual token never expires and covers the versions released while your updates or maintenance are in force. Each maintenance renewal gets you a new token for newer versions, and your existing token keeps working for the versions it covers. Existing Perpetual customers can request one too.

Treat tokens as secrets, and tell us within 2 business days if one is exposed. If the leak was accidental, we replace the token at no charge, and the leak alone is not grounds for termination. A deliberate or concealed leak can lead to termination. Once set, an offline token makes no license call, so we cannot switch it off remotely. Tokens identify the customer, and we can refuse a compromised token in later releases.

A non-expiring token does not depend on us or on the license service. If we ever intend to cease trading or permanently stop the license service with no successor, we commit in the EULA to give at least 90 days' notice and, to the extent we are lawfully able to, issue non-expiring tokens or builds without license validation to current Enterprise and Perpetual customers. You could then keep using the versions you are licensed for, without updates or support.

Redistributing EdiFabric as part of a product you sell needs the OEM rider on top of Enterprise. It includes derived serial keys for your end customers so they never handle yours. Processing other companies' EDI as a service is included in Enterprise, and in Perpetual for .NET and Native. It is not included in Developer. A Developer plan bought before November 2026 keeps this right until the end of its current term and through one further renewal, within its 3 leased seats and one production environment. Service bureau means processing third-party EDI on hosts you operate with ediFabric .NET, Native or a self-hosted Cloud API, including a SaaS product that processes its customers' EDI files. Exchanging your own EDI with your own trading partners is not service bureau. It does not let you resell our hosted Cloud as a competing translation API.

Not yet. Native ships X12 and HIPAA today, and the remaining standards are being released one at a time. ediFabric .NET and ediFabric Cloud already cover the full catalog, and every plan includes all three products, so every plan gives you every standard.

Once your order is complete, sign in to your account (using the email address you used for the purchase) to retrieve your serial key. For detailed steps, see this article. To upgrade, swap the serial key; your installation and code stay the same.

Developer and Enterprise renew automatically, provided the payment method on record has sufficient funds. You must keep the billing details up to date. If you cancel, the serial key stops working when the term ends.

Perpetual serial keys never expire. Maintenance is $600 per year after the first year and is only needed for further updates and support. Contact us at support@edifabric.com for a multi-year maintenance discount.

We reserve the right to suspend or reset serial keys if a leak is reported. Long-lived offline tokens are handled as described under “What happens if a token leaks?”.

Community and Developer are available to individuals. Perpetual licenses are sold only to legal entities that are not one-person consultancies, and the order must use a company email address. Public and disposable email addresses are declined. Long-lived tokens on any plan need a registered legal entity and a professional email address.

14-day money-back guarantee on your first purchase, counted from your first payment. Not the right fit? Full refund, no questions. It does not apply to renewals, maintenance or overage fees, and it ends once a long-lived token is issued.