Start with ADO.NET
Connect a .NET application, run a parameterized query, and use PostgreSQL types through familiar ADO.NET APIs.

Pick the outcome you need. We’ll take you to the right product, a working example, and the evidence behind it.
Six product areas that work together.
Connect .NET applications directly to PostgreSQL with familiar ADO.NET APIs.
ExploreUse LINQ, migrations, and tooling without giving up PostgreSQL-specific features.
ExploreTurn committed database changes into reliable, recoverable event streams.
ExploreKeep PostgreSQL, Redis, OpenSearch, and NATS destinations up to date.
ExploreAdd PostGIS, pgvector, TimescaleDB, and other features only when needed.
ExploreQuery connected data and keep graph results updated as PostgreSQL changes.
ExploreBlueTusk follows standard ADO.NET and EF Core patterns while exposing PostgreSQL features directly when your application needs them.
await using var dataSource =
new BlueTuskDataSourceBuilder(connectionString).Build();
await using var command = dataSource.CreateCommand(
"SELECT $1::int4 + $2::int4");
command.Parameters.Add(new BlueTuskParameter<int>(20));
command.Parameters.Add(new BlueTuskParameter<int>(22));
var answer = await command.ExecuteScalarAsync<int>();Types, schema objects, extensions, and SQL features stay first class across the provider and EF Core.
All 65 RC packages are public and clean consumer smoke passed. Stable 1.1 remains deliberately blocked on the exact stable-candidate programme, including endurance and PostgreSQL 19 GA.
Zero failures across the complete 45-assembly solution matrix.
Exact public surface across all six product families.
Machine-checked command, COPY, replication, EF, Live, Sync, and graph budgets.
Every NuGet and npm artifact is public at 1.1.0-rc.1 and passed clean consumer verification.
Every family shares one immutable version while stable-only gates stay explicit.
1.1.0-rc.1 public
RC public · stable 72-hour gate
RC public · stable 24-hour gate
1.1.0-rc.1 public
1.1.0-rc.1 public
RC public · PG 19 GA gate
Install the public packages, measure them against your own SLOs, report reproducible issues, or contribute evidence that strengthens the stable 1.1 release.