StudioHosting
STUDIO

Hosting

Serve Studio alongside your registered Runiq runtime.

Add Studio to the ASP.NET Core application that owns your AI capabilities. The API uses the name Dashboard; the developer interface is called Studio.

Enable local Studio

Install Runiq.AI.Core. This complete startup example enables the inspection surface only in Development:

Program.cs
using Runiq.AI.Core;

var builder = WebApplication.CreateBuilder(args);
builder.Services.AddRuniqServer();

var app = builder.Build();

if (app.Environment.IsDevelopment())
{
    app.UseRuniqDashboard(options =>
    {
        options.Authentication(auth => auth.AllowAnonymous());
    });
}

app.Run();

Open /runiq on the address printed by the host. This minimal host has no agents or indexes yet. Add capability registrations as shown in their guides.

In an existing application, extend its current AddRuniqServer(...) registration instead of adding a second one.

Customize the path and title

Inside the dashboard options callback, set:

Snippet
options.Path = "/dashboard";
options.Title = "My Application Studio";

Open /dashboard instead of /runiq after this change. The root path / is not supported. Keep an explicit authentication choice in the callback.

Use protected hosting

For Studio outside local development, configure the host authentication services and middleware, then select RequireAuthenticatedUser() or RequireRole(...).

Authentication shows a complete middleware example.

Check the host

SymptomCheck
Studio is absentEnvironment, configured path, and middleware registration.
Expected capability is missingIts registration in this running host.
UI loads but execution failsModel configuration, service dependencies, and application logs.
Access is deniedHost identity, roles, and chosen Studio access mode.

Changes to startup registrations require restarting the host. Studio does not maintain an independent copy of your application configuration.

On this page