Coordinate access changes
Connect
SPIRITT
TailscaleTailscale
Keep the tailnet intentional
SPIRITT puts Tailscale to work. Build network operations desks, manage approved device access, and keep routes and tags accountable.
What you can do with Tailscale.
Know what is connected
Join tailnet devices, users, routes, DNS configuration, and audit history into an operator-friendly view.
Apply precise access changes
Approve or revoke devices and replace route or tag sets using explicit, reviewed target values.
Verify the network state
Read back device changes, compare configuration snapshots, and track exceptions through your engineering workflow.
Works with your other apps.
Get started in three steps.
01
Open a workspace
Give SPIRITT a home for your Tailscale systems, connected tools, and ongoing work.
02
Connect Tailscale
Connect Tailscale alongside the apps your mission needs. Choose the account and working scope for your SPIRITT agent.
03
Hand over a mission
Describe the outcome. SPIRITT builds the system, executes the work, and follows through using your Tailscale connection.
Hand over a mission.
Choose a mission. Make it yours.
Put Tailscale to work.
Keep the tailnet intentional
Questions
Tailscale, with SPIRITT.
01What can SPIRITT do with Tailscale?+
SPIRITT can build network operations desks, manage approved device access, and keep routes and tags accountable. Join tailnet devices, users, routes, DNS configuration, and audit history into an operator-friendly view.
02Can SPIRITT build a custom system around Tailscale?+
Yes. A tailnet desk can show device identity and route state, maintain reviewed access-change requests, and verify each change against the intended configuration. SPIRITT builds the application and runs the connected workflow around your rules.
03Which Tailscale operations does this support?+
Tailscale supports device, user, DNS, settings, routes, and configuration-audit reads plus device authorization, route replacement, and tag replacement. Device approval changes require approval to be enabled. DNS and tailnet settings are readable here, not editable; tag and route changes replace complete sets.
04How does Tailscale work with my other apps?+
SPIRITT coordinates separately connected apps around one outcome. Coordinate access changes with Slack. Track network fixes with GitHub. Store tailnet snapshots with Supabase. You choose the accounts and actions it can use.
05Can SPIRITT own recurring follow-through?+
Yes. Read back device changes, compare configuration snapshots, and track exceptions through your engineering workflow. Set the schedule and approval rules; SPIRITT verifies results and keeps unresolved work assigned to an owner.
06How do I get started with Tailscale?+
Open a workspace, connect Tailscale, and hand SPIRITT a mission. Specify the records, outcome, and approval rules. Your connected account must have access to the operations the mission uses; additional apps are connected separately.