What Flushnet can do
Flushnet combines node registration, remote execution, browser automation, sandboxes, and distributed task orchestration into one operator layer.
Use your own machines, secure sandboxes, remote nodes, and AI-assisted control flows from one dashboard, API, or custom assistant.
Native machine control
Connect Windows or macOS machines as registered nodes and run commands, files, and automation tasks against them.
Secure sandbox execution
Test commands in sandbox or WebVM-style environments before promoting them to a real machine.
Browser automation
Run browser actions through the local agent, Playwright-compatible flows, and operator-style session control.
Multi-node orchestration
Dispatch work across multiple nodes and manage execution from a single account and dashboard.
Parallel job execution
Send the same class of task to more than one machine instead of waiting for serial execution on one host.
AI and compute workflows
Support AI jobs, remote compute tasks, file operations, automation pipelines, and GPU-oriented execution paths.
Realtime status
Track queued, running, failed, and completed work with async job state and dashboard visibility.
GitHub Actions integration
Trigger GitHub Actions workflows, inspect workflows, and check run status from the Flushnet API layer for repository-based jobs.
Dashboard, API, and assistant control
Operate Flushnet from the web dashboard, HTTP endpoints, or a custom AI assistant flow linked to your account.
Common use cases
- Run browser automation on a remote Windows node
- Dispatch the same task to multiple machines in parallel
- Test commands in sandbox before native execution
- Run file operations and shell tasks from one dashboard
- Control nodes from a custom AI assistant after linking access
- Control linked Tuya smart devices like plugs and sockets from chat
Why it is different
- Use your own machines instead of only rented cloud desktops
- Keep a safer sandbox path beside native execution
- Combine browser, terminal, file, and job workflows in one system
- Move from single-machine automation to distributed execution
- Keep the website, API, and assistant flows linked to the same control layer
Example actions
Illustrative examples
run command on win2_flushnet_node
list nodes for my account
run task in sandbox first
check async job status
power on the smart plug
power off the smart plug
status of the smart plug