Why should you care?

AgentNest business model depends on efficient tenancy — one ops team, hundreds of CRM and hospital customers.

See it live — copy this example

Paste into an ASP.NET Core 8+ / AgentNest project, then run with dotnet run (set your API keys in user-secrets).

// AgentNest.Api/Tenancy/TenantResolutionMiddleware.cs
public sealed class TenantResolutionMiddleware(RequestDelegate next)
{
    public async Task InvokeAsync(HttpContext ctx, ITenantStore tenants)
    {
        var host = ctx.Request.Host.Host;
        var tenant = await tenants.ResolveByHostAsync(host, ctx.RequestAborted);
        ctx.Items["Tenant"] = tenant;
        await next(ctx);
    }
}

What happened?

• Subdomain acme.agentnest.com resolves tenant Acme; downstream services read ctx.Items for quota, plugins, and vector namespace.
• Follow the steps below — typing the code yourself is the fastest way to learn.

Practice next

1. Map custom domains and subdomains to tenant records in SQL.
2. Scope every DB query and vector search with tenant id.
3. Billing meter reads AiUsageDaily per tenant.
4. Add tenant-specific custom domain SSL via App Service managed certs.
5. Shard large tenants to dedicated deployment group.

Remember

Resolve tenant from host or JWT early in pipeline. Isolate data, vectors, quotas, and plugins per tenant. Meter usage for SaaS billing.

SaaS onboarding

New hospital customer gets hosp-demo.agentnest.com in 15 minutes.

Outcome: Tenant middleware routes to hospital skills, Qdrant namespace, and stricter LLM options.