Blacksands Cyber
← All articles
Bursar — AI agents

The Developer Dashboard

The Developer Dashboard is the place to look at Bursar from a browser instead of asking an agent. It is where you see your agents, what each one can reach, your Receivers and the services behind them, and the architecture atlases you have uploaded. It sits alongside the tools your agent uses rather than replacing them: scanning code, granting access and revoking certificates still happen through your agent (see What can Bursar do?).

What you can see

The dashboard's navigation has these entries: Home, Apps, Agents, Access, Certs & sessions, DNS, Scan & atlases, Live topology, Receivers & services, Connect an agent, Plan & usage, Team and Settings. Two of them are placeholders for now: DNS is marked Locked, because DNS filtering is a separate add-on that is not part of the dashboard yet, and Team is marked Soon, because inviting teammates from the dashboard is not available yet. Between them the other pages answer the questions people ask most often:

  • Which agents do I have, and what can each one reach? Look at Agents, Access and Certs & sessions. The last one lists each agent's certificate and when it expires; a list of sessions is not available there yet. Each agent has its own certificate identity, and access is granted per service (see Understanding agent identities and scoped access).
  • What is protected, and by which Receiver? Look at Apps and Receivers & services.
  • What does my architecture look like? Look at Scan & atlases, and at Live topology under it. Atlases you upload from your agent on a paid plan are kept there as history; without an account, or on the free plan, an atlas is saved on your own machine, in your project's .bursar/atlas folder, as an HTML page with a JSON copy of the data beside it.
  • How do I add another agent? Start at Connect an agent. The install guide for every client has the steps for each client or framework.
  • What plan am I on, and how much of it am I using? Look at Plan & usage. It shows your usage, and your plan when it can be read; plan limits are not shown there yet (see Understanding your plan limits).

The navigation entries are the stable part. The dashboard is in beta, so what a page shows can change from one release to the next.

What you can do there

For now, everything in the dashboard is read-only. You can look, but you cannot change anything from it. To change something, ask your agent: it can grant or revoke an agent's access to a service, revoke a certificate, and pause or disable a service on a Receiver.

How you reach it

The dashboard is a protected service like any other on Blacksands, so there is no public login page. You reach it through the Authorizer and a Receiver, using a device certificate installed on the device you browse from. Without a valid device certificate the connection is refused, because Blacksands is fail-closed by design (see Connection denied: what it means). Access is by invitation on the beta, as described next.

Who can use it, and how to ask for access

On the beta the Developer Dashboard is invite-only. Ask your Blacksands contact to add you. If you do not have a contact, email info@blacksandsinc.com with your organization's name and say you would like Developer Dashboard access (see Contacting support for what to include).

Atlases and the direct link

When you upload an atlas from your agent with bursar_generate_atlas or bursar_publish_atlas (paid plans), it is kept as history in the dashboard. To have the upload result include a direct link to it, set the environment variable BURSAR_DASHBOARD_URL to the dashboard's https address on the machine that runs the Bursar MCP server. It is optional; without it the upload still works and you open the dashboard yourself. For the variables that carry an agent's credentials when it has no home directory that survives between runs, see the install guide.

Related reading