Download

Installing on Filters the installers, archives and commands below.

Packages

The components ship from a private package feed. Add the feed once, then install and update them like any other package.

Feeds and install commands are the same on Windows and Linux.

No package files are offered for download — the packages install only from this licensed feed, with your registry credential.

Registry credential

This is your personal username and token for the private Isabyte NuGet feed (nuget.debiansrv.ddns.net) — NuGet sends both as Basic authentication on every package download, and they work while your license is active; generate, regenerate or revoke them on the Credentials page of your Isabyte account.

Manage your registry credential

Where the commands below show <USERNAME> or <TOKEN>, put in your own values from the Credentials page; this page never shows them.

Blazor Power ToolsFeed livev1.10.1137

Add the feed

dotnet nuget add source https://nuget.debiansrv.ddns.net/v3/index.json --name Isabyte --username <USERNAME> --password <TOKEN> --store-password-in-clear-text

Install

dotnet add package Isabyte.PowerTools.Blazor --version 1.10.1137

dotnet add package Isabyte.PowerTools.Blazor.AI --version 1.10.1137

Update

dotnet add package Isabyte.PowerTools.Blazor # re-run to pull the latest

dotnet add package Isabyte.PowerTools.Blazor.AI # re-run to pull the latest

The VS Code extension, the isabyte-setup tool and the Isabyte Expert MCP server have their own page. Open the Code plugins page

AI Skillsets Bundle

Structured markdown skill files that teach your AI coding assistant the full Isabyte Power Tools API surface — components, parameters, usage patterns and whole-app scaffolding. They are plain markdown, so every popular agent client can use them; the setup per client:

Claude Code

Unzip into .claude/skills/, then initialize the project so the agent indexes them into its project memory:

mkdir -p .claude/skills && unzip isabyte-claude-skillsets.zip -d .claude/skills
claude   # then run /init — CLAUDE.md will reference the skills

OpenAI Codex

Unzip anywhere in the repo and point AGENTS.md at the files:

mkdir -p docs/isabyte-skills && unzip isabyte-claude-skillsets.zip -d docs/isabyte-skills
echo "Read docs/isabyte-skills/README.md before using Isabyte Power Tools." >> AGENTS.md

opencode

Same AGENTS.md convention as Codex — one instruction file, shared:

mkdir -p docs/isabyte-skills && unzip isabyte-claude-skillsets.zip -d docs/isabyte-skills
# opencode reads AGENTS.md automatically

Cursor

Drop the files into the rules directory:

mkdir -p .cursor/rules/isabyte && unzip isabyte-claude-skillsets.zip -d .cursor/rules/isabyte

GitHub Copilot

Reference them from the repository instructions file:

mkdir -p docs/isabyte-skills && unzip isabyte-claude-skillsets.zip -d docs/isabyte-skills
echo "See docs/isabyte-skills/ for Isabyte Power Tools guidance." >> .github/copilot-instructions.md

Claude Projects / any API client

Upload the files as project knowledge, or include the relevant skill file in the system prompt when calling the API.

Download Blazor skillsets (.zip)

The Blazor bundle is generated from the shared component manifest; the master bundle adds the design-system and app-scaffolding deep-dive skills. Both are free to download — the components check your license key when your app runs.

Server Monitor Service

Install the Isabyte Server Monitor agent on any machine in your network to stream real-time CPU, GPU, memory, network, and process metrics back to your dashboard. Runs as a lightweight background service on Windows and Linux.

Showing the Linux agent. Change it at the top of the page.

Download Packages

isabyte-servermonitor_1.10.1137_amd64_debian-12.deb (27.4 MB)isabyte-servermonitor_1.10.1137_amd64_debian-13.deb (27.4 MB)isabyte-servermonitor_1.10.1137_amd64_ubuntu-22.04.deb (27.4 MB)isabyte-servermonitor_1.10.1137_amd64_ubuntu-24.04.deb (27.4 MB)isabyte-servermonitor_1.10.1137_x86_64_centos-stream-10.rpm (34.5 MB)isabyte-servermonitor_1.10.1137_x86_64_centos-stream-9.rpm (34.5 MB)isabyte-servermonitor_1.10.1137_x86_64_rocky-10.rpm (34.5 MB)isabyte-servermonitor_1.10.1137_x86_64_rocky-9.rpm (34.5 MB)

Install the Package

Download and install the .deb package (Ubuntu/Debian):

sudo dpkg -i isabyte-servermonitor_1.10.112_amd64.deb

Or the .rpm package (Rocky/CentOS/RHEL):

sudo dnf install ./isabyte-servermonitor_1.10.112_x86_64.rpm

Configure the Hub Connection

Edit the configuration: set the ingest URL of your dashboard host and paste in the shared monitor key:

sudo nano /opt/isabyte-servermonitor/appsettings.json

{
  "ServerMonitor": {
    "HubUrl": "https://your-dashboard-host/isabyte-servermonitor-ingest",
    "MonitorKey": "<your monitor key>",
    "ServerId": "my-linux-server",
    "IntervalMs": 2000
  }
}

The monitor key is the shared secret every Server Monitor agent sends in the X-Isabyte-Monitor-Key header and your app's ingest route checks before it accepts metrics — one value of at least 32 characters, set as ServerMonitor:MonitorKey on every server and in your app; generate and keep it on the Credentials page of your Isabyte account, or create your own.

Get or manage your monitor key

Start and Enable the Service

sudo systemctl enable --now isabyte-servermonitor

Verify it's running:

sudo systemctl status isabyte-servermonitor

Service configuration reference

Setting	Description	Default
`HubUrl`	The push-only ingest URL on your app or on the collector (path `/isabyte-servermonitor-ingest` by default)	(required)
`MonitorKey`	The shared monitor key, sent in the `X-Isabyte-Monitor-Key` header. Use the same value on every server and in your app; a missing or wrong key is refused with `401`. Can also be set with the environment variable `ServerMonitor__MonitorKey`.	(required)
`ServerId`	Unique identifier for this server	Machine hostname
`IntervalMs`	How often to push metrics (milliseconds)	2000
`ShowCPU`	Collect CPU usage (total and per core)	true
`ShowGPU`	Collect GPU metrics (NVIDIA GPUs, via `nvidia-smi`)	true
`ShowMemory`	Collect memory usage	true
`ShowNetwork`	Collect network throughput metrics	true
`ShowProcesses`	Collect the top processes by CPU and memory	true
`ShowSystemInfo`	Collect OS, hostname, uptime and CPU model	false
`ShowServerLogs`	Stream new lines from the files listed in `LogFiles`	true
`LogFiles`	Paths of the log files to stream	[]

Firewall & networking

The monitor service makes outbound HTTPS connections to your dashboard host. Ensure:

The service can reach the dashboard host on the configured port (typically 443).
No firewall rule blocks outbound HTTPS from the monitored server.
Behind a reverse proxy (nginx, IIS), WebSocket upgrade headers are forwarded.
On internal networks, an internal DNS name or IP works fine as the HubUrl.

Tip Test connectivity from the monitored server before deploying the service:

curl -I https://your-dashboard-host/isabyte-servermonitor-ingest

A 401 reply is expected here: it proves the route is reachable, and curl sends no monitor key.

Connect your Server Monitor dashboard

Your dashboard reads live from your own app: register the monitor once (AddIsabyteServerMonitor()), map the ingest route (MapIsabyteServerMonitorIngest) and the dashboard hub (MapIsabyteServerMonitorHub), point each agent's HubUrl at the ingest route, and render the component:

@using Isabyte.PowerTools.Components.Tools

<IsabyteServerMonitor Servers="@servers" />

Tip Every agent uses the same HubUrl and MonitorKey. Protect the dashboard hub with your app's own login by chaining .RequireAuthorization() on it.

Component Demos

Explore every component with live interactive examples.

Pricing

One plan, everything included.