BLUETUSK 1.1.0-RC.1 · PUBLIC

The PostgreSQL platform for .NET

Use one PostgreSQL-native stack for ADO.NET, EF Core, replication, real-time delivery, extensions, and graph. Start small, add only what you need, and verify every release through published evidence.

BlueTusk architecture: .NET applications connect through Provider and EF Core to PostgreSQL. Streams then powers Sync, Live, and Continuous Graph while Control Plane observes the runtime. Sync delivers to Redis, NATS, and OpenSearch; Live delivers to applications.
Architecture overviewProvider → PostgreSQL → Streams → Sync · Live · Graph
  1. 01 · BUILD.NET applicationsADO.NET · EF Core
  2. 02 · CONNECTBlueTusk ProviderPooling · types · COPY
  3. 03 · STOREPostgreSQLSQL · WAL · extensions
  4. 04 · REACTStreamsCommitted changes · checkpoints
  5. 05 · DELIVERSync · Live · GraphDestinations · clients · projections
CHOOSE YOUR ENTRY POINT

Start from the job in front of you.

Pick the outcome you need. We’ll take you to the right product, a working example, and the evidence behind it.

11/11 live compatibility

Start with ADO.NET

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

Explore Provider
THE ECOSYSTEM

Engineered for the modern PostgreSQL stack

Six product areas that work together.

FAMILIAR .NET. NATIVE POSTGRESQL.

Start with a connection.
Keep every capability.

BlueTusk follows standard ADO.NET and EF Core patterns while exposing PostgreSQL features directly when your application needs them.

  • Typed parameters, never SQL interpolation
  • Async data paths and bounded resource use
  • Native COPY, replication, and type support
  • First-class diagnostics and release evidence
Program.cs
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>();
POSTGRESQL, FULLY EXPOSED

The database stays powerful.

Types, schema objects, extensions, and SQL features stay first class across the provider and EF Core.

01Types

PostgreSQL’s type system, without flattening it

ArraysRangesMultirangesCompositesEnumsJSONBNetworkFull text
02Database design

Schema features that stay PostgreSQL-native

PartitioningRow-level securityPublicationsSubscriptionsScaffoldingMigrations
03Specialized workloads

One provider, deeper capabilities

PostGISpgvectorTimescaleDBpg_durableSQL/PGQLogical replicationPipeline mode
1.1 RC RELEASE EVIDENCE · 29 AUG 2026

Published, verified, and explicit about the boundary.

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.

3,289

PostgreSQL 19 passes

Zero failures across the complete 45-assembly solution matrix.

13,056

Budgeted API signatures

Exact public surface across all six product families.

46

Allocation budgets

Machine-checked command, COPY, replication, EF, Live, Sync, and graph budgets.

65 / 65

Public RC packages

Every NuGet and npm artifact is public at 1.1.0-rc.1 and passed clean consumer verification.

RELEASE TRAINS

One public RC. Stable confidence is still earned.

Every family shares one immutable version while stable-only gates stay explicit.

01

Provider

1.1.0-rc.1 public

02

Streams

RC public · stable 72-hour gate

03

Sync

RC public · stable 24-hour gate

04

Live

1.1.0-rc.1 public

05

Control Plane

1.1.0-rc.1 public

06

Continuous Graph

RC public · PG 19 GA gate

BUILD WITH BLUETUSK

Put the 1.1 release candidate under a real workload.

Install the public packages, measure them against your own SLOs, report reproducible issues, or contribute evidence that strengthens the stable 1.1 release.