Altostrat SDX is easier to use when you separate the things you manage from the systems that carry out the work. A site is the object you see in the portal. The device job plane, management tunnel, metadata store, and workflow engine are the systems that keep that site useful.Documentation Index
Fetch the complete documentation index at: https://altostrat.io/docs/llms.txt
Use this file to discover all available pages before exploring further.
Organization Model
Organization
The top-level account boundary. Organizations contain workspaces, users, teams, billing settings, and governance configuration.
Workspace
The tenancy and billing container. Workspaces hold the SDX resources your team operates.
Team
The collaboration boundary for day-to-day access. Teams collect users and apply roles to the resources they can work with.
Role
A permission set. Portal navigation and actions are scope-gated, so users only see what their role allows.
Network Objects
Site
A site represents a managed MikroTik router and its operational context: status, tunnel information, metadata, tags, notes, backups, metrics, faults, and feature assignments.
Management VPN
The outbound management path between a site and Altostrat regional infrastructure. It supports remote access, synchronous commands, and management-side operations.
Policy
A reusable configuration object that can be attached to one or more sites. Examples include control plane, content filtering, BGP threat, security group, and prefix list policies.
Tag and Metadata
Structured context you attach to sites and other resources. Tags support filtering, reporting, workflow conditions, and operational ownership.
Execution Concepts
Heartbeat
A regular check-in from the router. Heartbeats feed online status, last-seen data, device inventory, and availability reporting.
Device Job
A queued unit of work for a router. Scripts, backup requests, policy pushes, ARP syncs, VPN updates, and selected feature actions all use the same job pattern.
Synchronous Command
A live command sent through the management server when the site is reachable. Use this for current state, not for reading static configuration you can get from backups.
Workflow Run
One execution of a workflow. Runs have triggers, node results, logs, and context passed between actions and conditions.
Operational Concepts
Fault
A normalized operational incident, such as a site outage or WAN state change. Faults feed dashboards, notifications, workflows, and SLA reporting.
Schedule
A reusable time window. Schedules can control when automations, reports, scripts, and notifications should run or deliver.
Notification Group
A routing rule for who gets told about operational events, and through which channels or integrations.
Report
A generated operational artifact, such as an SLA report or vulnerability report, built from stored platform data.
Next Step
Read the Operating Model
Learn how heartbeats, jobs, live commands, faults, notifications, and reports behave in real operations.