Sign up free

Products FAQs Last updated: 2026-09-30

ediFabric translates EDI to structured JSON or typed objects and back, validates it and generates acknowledgments. It comes as three products that share the same EDI models and one serial key, and every plan includes all three.

What is the difference between ediFabric .NET, Native and Cloud?

ediFabric .NETediFabric NativeediFabric Cloud
What it is.NET library (.dll)Native library (.dll, .so, .dylib)REST API hosted by us
LanguagesC# and any other .NET languagePython, Java, C, C# and any language that can call a C libraryAny language that can make an HTTPS request
InstallNuGet package or DLLOne library file per platform, plus the bindingsNothing to install
RunsIn your environmentIn your environmentIn our cloud
Works offlineYesYesNo
Maximum file sizeUnlimitedUnlimited3 MB per request
EDI standardsAll ten, plus custom flat filesX12 and HIPAA, more to followAll ten
EDI modelsC# templatesOpenEDI JSON modelsOpenEDI JSON models

The product comparison has the full list of differences.

Which product should I use?

Use ediFabric .NET in a .NET application; it has the full standard catalog, custom flat files, large file splitting and database scripts. Use ediFabric Native to translate X12 and HIPAA in process from Python, Java, C or any other language. Use ediFabric Cloud to call a REST API from anywhere without installing anything, for every standard.

For PHI or other regulated data, use .NET or Native, which never send EDI data out of your network, or host the same API yourself. See HIPAA and SOC 2.

Which EDI standards does each product support?

ediFabric .NET and ediFabric Cloud support all ten standards: X12, HIPAA, EDIFACT, EANCOM, IATA PADIS, HL7, NCPDP, VDA, IAIABC and EDIGAS. ediFabric .NET also reads and writes custom flat files and CSV. ediFabric Native supports X12 and HIPAA today, and the remaining standards are being released one at a time. A plan never limits which standards you can use.

Which EDI versions and transactions are included?

Every version and transaction below is included in every plan, as C# templates for ediFabric .NET and as OpenEDI models for Native and Cloud:

The EDI transactions section has the structure, a sample file and code for the most used ones. If your transaction or version is not listed, let us know. To work out the version of a sample file, see how to find the EDI version.

Which .NET versions does ediFabric .NET support?

.NET 8, 9 and 10 on Windows, Linux and macOS, including cloud hosting on Azure and AWS, and .NET Framework 4.8 on Windows.

What is included in ediFabric .NET?

  • The EdiFabric NuGet package, or the DLL for projects without access to nuget.org
  • A template NuGet package per standard: EdiFabric.Templates.X12, .Hipaa, .Edifact, .Hl7, .Ncpdp, .Padis, .Vda and .Edigas
  • The EDI templates as C# source files, to adapt to your trading partners' implementation guides
  • Entity Framework DbContext files and database scripts for X12 and EDIFACT
  • C# examples for every operation, on GitHub

It parses EDI into typed C# objects, generates EDI from them, validates transactions, generates X12 997, 999 and TA1 and EDIFACT CONTRL acknowledgments, serializes to JSON and XML, splits large transactions, and reads and writes custom flat files and CSV. The introduction shows how to install it.

Which platforms does ediFabric Native run on?

Windows x64 (edifabric-x12-tools.dll), Linux x64 (edifabric-x12-tools.so) and macOS arm64 (edifabric-x12-tools.dylib). There are official bindings for Python, Java, C and C#, and any other language can use the C ABI. The Windows binaries are Authenticode-signed, the Linux binaries have a detached signature and the macOS binaries are codesigned. The introduction has the downloads.

How do I apply my serial key?

The same serial key works for all three products:

  • ediFabric .NET: call License.SetSerial("YOUR_SERIAL_KEY"); before any other call.
  • ediFabric Native: call set_serial in the bindings for your language, after loading the library.
  • ediFabric Cloud: send the key on every request in the Ocp-Apim-Subscription-Key header.

There is no license file. See how to install your serial key.

Does my EDI data leave my network?

Not with ediFabric .NET or ediFabric Native: every operation runs inside your own application. With ediFabric Cloud, the files are sent to our service and processed there.

Can I customize the EDI templates and models?

Yes. In ediFabric .NET, templates are C# classes that you can copy and change. ediFabric Native and ediFabric Cloud use OpenEDI JSON models; in Cloud, private custom models are available on Developer, Enterprise and Cloud only, and Community uses the public models.

Do ediFabric .NET and ediFabric Native use the same engine?

No. ediFabric .NET runs on the established .NET engine, with the full standard catalog and years of production use. ediFabric Native is the next-generation engine. EdiNation already runs on Native, and ediFabric Cloud runs on the .NET engine today, with a move to Native on the roadmap. ediFabric .NET stays on its engine, so existing .NET applications keep working without a rewrite.

What is EdiNation?

EdiNation is a free EDI editor in the browser. It views and validates EDI files, converts SEF files and documents every EDI specification in its spec library. It runs on the Native engine, so the EDI never leaves the browser tab.

How often are new EDI templates released?

New versions are released when there is demand, or when a new version differs significantly from the latest one we offer. You can also request new templates by contacting us.

How do I request a demo?

Email office@edifabric.com to schedule one. It takes 30 to 60 minutes, and we show the product features and how to use them.

How do I upgrade from the open-source EdiFabric Framework?

Everyone still using an open-source EdiFabric Framework version, such as 7.3.1 or 8.0.1, is entitled to a 15% discount on upgrading to the latest version if they are willing to feature in a case study. Contact office@edifabric.com for details.