Build .NET applications connected to your IBM i
With NTi Data Provider, access your DB2 for i data and IBM i resources from .NET to build modern, cross-platform applications.
View the documentation
Why .NET is the obvious choice today
The standard for modern development.
One platform,
every use case
Web, API, mobile, desktop, cloud, AI. With .NET, you build everything in C# using the same tooling and the same team.
Open source,
public roadmap
Developed on GitHub since 2016, annual releases, guaranteed LTS support. No proprietary dependencies.
The global
enterprise standard
From SMEs to large industrial groups, .NET is widely adopted for business applications deployed at scale.
What .NET brings to IBM i
Skills
C# is the 5th most used language on GitHub. A large, active talent pool that is easier to recruit from.
Industrialisation
With .NET, your IBM i fits into a modern development cycle. Unit testing, Git versioning, and CI/CD pipelines can be applied around the system.
Cross-platform
Windows, Linux, Docker, IBM Power. A single .NET application connected to your IBM i, deployed anywhere, with no infrastructure constraints.
IBM i as a back end
Your business logic stays on IBM i. Everything else is written in .NET.
An ADO.NET provider
for DB2 for i
For a .NET developer, the learning curve is zero. Open a connection, run a query, read the result, just like any other database: standard C# applied to IBM i.
Build REST APIs
in just a few lines
With ASP.NET Core, a single minimal route is enough to expose DB2 for i as a REST API. NTi integrates with no special configuration: same code, same habits, only the provider changes.
An EF Core extension
built for DB2 for i
For projects built around Entity Framework Core, NTi provides a full extension: DbContext, migrations, LINQ, change tracking, and DB-first or code-first scaffolding.
Full IBM i
control from C#
NTi goes beyond data. The same connection lets you run CL commands, call RPG programs, and orchestrate IBM i processing from any .NET application.
New use cases for your IBM i
Extend its capabilities, with .NET and NTi.
Web services
Replace your green screens with modern web interfaces. Your existing business logic stays on IBM i, everything is called from the .NET side.
AI and MCP
Build a .NET MCP server to let an AI model (Claude, GPT...) query your IBM i directly.
Mobile and field
Android and iOS apps connected in real time to your IBM i. Barcode scanning, inventory, field data entry, with no middleware.
Cloud and containers
Connect your IBM i to Azure, AWS, or Google Cloud. Deploy your .NET applications in Docker containers on Linux, ARM, or IBM Power.
IBM i natively accessible from .NET
Quickly assess the value on a real use case.
Any questions?
Like Java, .NET is today one of the most mature development platforms available: fast, modern, open source, and cross-platform. It lets you build web, mobile, desktop, cloud, and microservices applications using a single language, C#.
.NET was ranked the #1 most-loved framework in the Stack Overflow Developer Survey for three consecutive years.
For an IBM i project, .NET brings a standardised, productive, and sustainable environment, backed by a large pool of readily available skills on the market.
Yes.
Simply add the Aumerial.EntityFrameworkCore NuGet package from .NET, then register your DbContext with UseNTi().
NTi EF Core lets you work with DB2 for i just like any other .NET database: you write C#, query your tables via LINQ, have SQL generated automatically, and create your schema using a code-first approach or reverse-engineer an existing one with DB-first.
The EF Core extension handles DB2 for i-specific features such as BLOB types and global length configuration (VARCHAR, VARBINARY, VARGRAPHIC).
Yes. NTi lets you run CL commands, call RPG/CLP programs, and even invoke IBM i system APIs.
CL commands and IBM i program calls are handled through the dedicated AS-RMTCMD server, removing any need for SQL in these use cases.
Yes.
The .NET approach with NTi is built on a clear separation of concerns: IBM i retains the data and business logic, while .NET handles the application layer by consuming existing data, programs, and commands, with no duplication of logic.
This approach makes it possible to introduce new capabilities incrementally, such as web interfaces, APIs, or mobile applications, while keeping IBM i as the business foundation.
Yes.
The application lifecycle sits on the .NET side, which remains a standard development platform. Applications built with NTi can be tested, versioned, built, and deployed using the usual .NET ecosystem tooling, independently of the IBM i back end.
Business processing continues to run on IBM i, while code quality, automation, and deployment are managed on the .NET side, following modern enterprise development practices.
