Start free with all three
- For C# and any other .NET language
- Distributed as a NuGet package or a DLL file
- Minimum .NET 6 or .NET Framework 4.8
- All ten EDI standards, plus custom flat files
- Offline and online mode
- For C, C++, Rust, Go, Python, Node.js, Java
- A single library file per platform
- Multiplatform - Windows, macOS, Linux
- X12 and HIPAA, more standards to follow
- Offline and online mode
- For any language that can call a REST API
- No software installation needed
- All ten EDI standards, nothing to maintain
- Your EDI data is processed on our servers
- Online mode only
All EDI products in a nutshell
| ediFabric .NET | ediFabric Native | ediFabric Cloud | |
|---|---|---|---|
| What is it? | .NET library (.dll) | Native library (.dylib, .so, .dll) | Cloud REST API |
| Translation engine | Classic .NET engine | Next-generation Native engine | Classic .NET engine today; Native is on the roadmap |
| Which languages can call it? | C# and any other .NET language | C, C++, Rust, Go, Python, Node.js, Java, .NET - anything that can call a C library | Any language that can call a REST API |
| How to install it? | Install a Nuget package or reference a DLL | Import a native library with C entry points | No installation is required |
| Included files | EdiFabric.dll, EDI Templates as C# files, Entity Framework DbContext files | edifabric-x12-tools.dll, edifabric-x12-tools.so, edifabric-x12-tools.dylib | No files |
| Can it work offline? | Yes, online and offline modes are supported | Yes, online and offline modes are supported | No, only online mode |
| Where does it run? | In your environment | In your environment | In our cloud |
| Would the contents of your EDI files leave your network? | No | No | Yes |
| Maximum file size allowed | Unlimited | Unlimited | Up to 3 MB |
| Translates EDI data into structured JSON? | Yes, into typed C# objects that serialise straight to JSON | Yes, into JSON | Yes, into JSON |
| Translates structured JSON back into EDI? | Yes | Yes | Yes |
| Supported EDI standards | EDIFACT, EANCOM, X12, HIPAA, IAIABC, NCPDP, HL7, VDA, EDIGAS, IATA | X12 and HIPAA today. The remaining standards are being released one at a time | EDIFACT, EANCOM, X12, HIPAA, IAIABC, NCPDP, HL7, VDA, EDIGAS, IATA |
| Supports custom flat files? | Yes | No | No |
| Supports splitting for large files? | Yes | Yes | No |
| Includes database scripts for X12 and EDIFACT? | Yes | No | No |
| Includes templates/models for all EDI messages? | Yes, as C# files | Yes, for X12 and HIPAA, as OpenEDI JSON files | Yes, as OpenEDI JSON files |
| Supports custom EDI models/templates? | Yes, as C# files | Yes, as OpenEDI JSON files | Yes, as OpenEDI JSON files |
| How is it licensed? | Included in every plan | Included in every plan | Included in every plan |
| What support do you get? | Set by your plan | Set by your plan | Set by your plan |
| Online documentation | Yes | Yes | Yes |
Two engines, one product family
ediFabric .NET and ediFabric Native are built on two separate translation engines. Native is the next-generation engine. The .NET library is the established engine - the one with the full standard catalog and years of production use.
EdiNation, the browser editor, already runs on Native, so EDI never leaves the tab. ediFabric Cloud still runs on the .NET engine today.
The roadmap is to move Cloud onto Native. After that, Native, EdiNation, and Cloud will share the latest engine. ediFabric .NET stays on the classic engine, so existing .NET apps keep working without a rewrite.