Nest by Swanatronics

Where your bots live.

Nest is the Swanatronics runtime layer for managing bots across Linux systems using systemd, SSH, passwordless key access, service visibility, alerts, jobs, deployments, and safer operator control.

Status Alpha v0.0.4
Runtime systemd + SSH
Release Goal V1
Bot-Centric Infrastructure

Built around the bot, not just the server.

Nest is moving toward a bot-first control centre: inventory, health, deployments, jobs, logs, alerts, and guarded remote actions all tied to the services that matter.

🖥️

Connect Linux nodes

Add Linux systems that support systemd and SSH, then use passwordless SSH keys for controlled service management.

🧰

Manage bot services

View bot state, resource usage, logs, restarts, deploy history, scheduled actions, and job results from one place.

🔐

Control who can do what

Keep access structured with Admin, Operator, and Viewer roles while avoiding an extra Owner role during the alpha phase.

Feature Stack

The control layer for running bots properly.

The direction is clear: less terminal chaos, more safe actions, better visibility, and a proper SaaS-grade interface around the bots you already run.

01

Bot inventory

Track every managed bot, where it runs, what service owns it, current state, version, and operational notes.

02

Deploy history

Record what changed, when it changed, who triggered it, target node, version, output, and rollback context.

03

Scheduled actions

Queue restarts, deploy windows, checks, maintenance tasks, and controlled actions without babysitting the terminal.

04

Health score

Summarise service state, resource pressure, recent failures, stale deploys, alert noise, and node condition.

05

Remote operations

Remote file browser, restricted terminal, package deployments, and safe operator tools with clear guardrails.

06

Monitoring dashboard

CPU, RAM, uptime, services, jobs, alerts, trends, logs, node groups, and operational signals in one dashboard.

Full Mapped Plan

From Alpha v0.0.4 to V1.

This is the complete Nest direction we mapped: alpha cleanup first, then bot-centric operations, deployment control, safer remote tools, monitoring, and scale-ready node management.

Pass 2

Alerts Centre

Split alerts into clear operational views instead of one noisy pile.

  • Active Alerts
  • Thresholds
  • History
  • Status
Pass 3

Jobs tab rebuild

Turn jobs into a proper operator table with useful detail and recovery controls.

  • Retry action
  • Output view
  • Duration
  • Target and filtering
Pass 4

Audit revamp

Make audit history readable, searchable, and useful when something needs traced.

  • Clear headings
  • Table layout
  • Action metadata
  • Operator accountability
Runtime

Bot operations

Move beyond basic service state into real bot management.

  • Bot inventory
  • Service log improvements
  • Health score
  • Monitoring dashboard
Deploy

Deployment control

Give every release a record and every operator a safer path.

  • Deploy history
  • Version deployment
  • Deploy profiles
  • Package deployments
Remote

Guarded remote tools

Add powerful tools without turning the app into a free-for-all shell.

  • Remote file browser
  • Restricted terminal
  • Scheduled actions
  • Backups and restore
Scale

Multi-node future

Prepare Nest for more systems, more bots, and cleaner onboarding.

  • Multi-node groups
  • Node onboarding
  • Permission-aware actions
  • V1 public release path
Operator Flow

Run the scary stuff with guardrails.

The goal is not to hide power. The goal is to make restarts, deploys, file operations, package installs, and terminal actions safer by showing context before action.

deploy-profile: sentinel-v1 Requires Admin
Target verified

Node, service, and branch match the selected deploy profile.

Output captured

Job duration, command result, and deploy notes are attached to history.

Rollback context ready

Previous version and restart state are visible before final confirmation.

Access Model

Simple roles while the product grows.

During alpha, Nest keeps access focused: Admin, Operator, and Viewer. No separate Owner role for now, because there should only be one owner while the product is still in development.

Admin

Full operational control

Manage nodes, services, jobs, deploys, alerts, settings, and higher-risk actions.

Operator

Run approved actions

Restart services, view jobs, inspect logs, respond to alerts, and operate within limits.

Viewer

Read-only visibility

View bot status, health, logs, audit history, alerts, and monitoring without changing state.

Nest

Control the runtime.

Nest is the infrastructure side of the Swanatronics ecosystem: the place where bot services become visible, controlled, and ready for V1.