How Tenantry compares
Tenantry beside the options most .NET teams weigh, as each project documents itself.
| Your own query filters | Finbuckle.MultiTenant | ABP | Tenantry | |
|---|---|---|---|---|
| What your DbContext needs | A filter on each entity, and a SaveChanges override | Derive from MultiTenantDbContext, or implement IMultiTenantDbContext and call EnforceMultiTenant() in SaveChanges | Derive from AbpDbContext, in an ABP application | One call, options.UseTenantry() |
| Create and migrate tenant databases | You write it | No | Yes, in the commercial SaaS module | Yes, in Pro |
| Per-tenant options and authentication | You write it | Yes, both | Per-tenant settings and features | Yes, both |
| Licence | Yours | Apache-2.0 | A commercial ABP licence for the SaaS module | Core Apache-2.0; Pro a subscription |
- Writes
- Finbuckle checks the entities EF Core tracks before saving, and by default throws when one belongs to another tenant. Tenantry rejects those writes too, and also puts the stored tenant in every UPDATE and DELETE, so a forged key changes no rows. ExecuteUpdate and ExecuteDelete are filtered to the current tenant, and cannot set TenantId.
- No tenant
- With no current tenant, Tenantry’s filter matches nothing and tenant-scoped writes are rejected. Finbuckle throws when a multi-tenant entity is saved with no tenant.
- A database per tenant
- Tenantry supports a database per tenant with pooled contexts (AddDbContextPerTenantDatabase with pooled: true). Finbuckle’s docs do not cover pooling. ABP’s SaaS module, and Tenantry Pro, create and migrate tenant databases; Finbuckle leaves that to you.
- Options and authentication
- Core gives options, named options included, the current tenant’s values, so each authentication scheme can have a tenant’s own settings. app.UseTenantResolution() makes the tenant current before authentication, and tenants on different identity providers each get a scheme of their own. ASP.NET Core Identity works with its own IdentityDbContext and a user type that implements ITenantEntity.
- What Tenantry does not do
- Tenantry is a library, not an application framework: there is no admin UI or tenant management screen, as ABP has. It builds in one tenant store, which holds tenants in memory. Finbuckle also has stores that read tenants from configuration, a distributed cache or an HTTP service.
- .NET versions
- Finbuckle.MultiTenant 10 targets .NET 10 only. Tenantry supports .NET 10, and .NET 8 and 9 until November 2027.
Moving from Finbuckle.MultiTenant? The migration guide takes a Finbuckle application to Tenantry step by step.
Checked in October 2026 against each project’s documentation. Something out of date? Email support@tenantry.dev.