FlowForge datasheet | Rudratic Technologies

Agentless IT automation

FlowForge

Rudratic Technologies

Workflows across Linux, Windows and network gear, with nothing installed on the hosts

FlowForge runs workflows across Linux and Windows servers and network switches over native SSH and WinRM, with no agent on the targets. Workflows are built as a graph on a canvas or drafted by an AI assistant from one sentence, then run automatically, step by step through manual gates or on a cron schedule, with output streamed live. Every execution, terminal command and configuration change is written to an immutable audit ledger.

The problem

Scripts and cron jobs hide what is happening while they run and stop at the first failure, so the steps after it never run and nobody finds out until morning. Long jobs die with the session that started them, and there is no record of who ran what, on which host.

0Agents installed on target hosts
50Workers running steps in parallel, at most
3Ways to run a step: direct, detached, interactive

Core capabilities

Agentless execution

SSH on port 22 to Linux hosts and network switches
WinRM on port 5986 to Windows, or OpenSSH after migration

Visual workflow graph

Steps dragged onto a canvas from Start to End
Pre-flight check for circular dependencies and missing targets

AI assistant

Drafts a workflow graph from a plain-language description
Reads a failed step’s stderr and suggests a fix

Three ways to run a step

Direct: streams logs live and ends on the exit code
Detached inside screen, or interactive for mid-run prompts

Gates and schedules

Automatic, step by step through manual gates, or on cron
Every run kept in the execution log

FlowForge datasheetPage 1 of 2

Enterprise capabilities

Roles with hard boundaries

Super Admin, Administrator and Standard user
Enforced in the interface and at the REST API; no self-registration

Directory sign-in

Binds to Active Directory or LDAP, then checks a local profile
Local Super Admin fallback when the directory is down

Credentials and audit

Passwords and .pem or .key files encrypted with AES-256-GCM
Ledger of time, user, target, action and client IP

Durable sessions and transfers

Browser terminal over WSS, kept alive inside screen
4 MB chunks, each checked with SHA-256, resumed after a drop

Platform modules

Dashboard: Workflow, server and run counts, the ten latest executions and the worker pool.
Workflows: The canvas editor, with each step shown running, completed, failed or at a gate.
Servers: Hosts added one by one or synced from cloud inventory, with a live handshake test.
Terminal: A browser terminal that keeps running when the laptop closes.
Audit logs: The execution and change ledger; standard users see only their own.
Templates: Pre-approved runbooks, such as a disaster-recovery drill, run in one click.
GitHub: Runbooks, scripts and workflow YAML pulled from your organisations on every commit.
Analytics: Workflow reliability, SLA compliance and throughput across the fleet.
Alerts: SLA breaches and failed runs sent to webhooks, Slack or Microsoft Teams.
Feature toggles: Whole modules switched on or off across the platform.

Technical specifications

Targets	Linux (Bash, Zsh), Windows and network switches
Protocols	SSH on 22, WinRM on 5986, SFTP for transfers, WSS to the browser terminal
Agents	None on target hosts
Parallel runs	Worker pool with a hard cap of 50
Encryption at rest	AES-256-GCM for passwords and key files
Sign-in	Active Directory or LDAP bind with a local profile; local Super Admin fallback
AI models	OpenAI, Anthropic or a local Ollama for air-gapped sites
Log forwarding	Telemetry, sign-in events and workflow logs to SIEMs such as Datadog or Splunk

Works with

GitHub
Slack
Microsoft Teams
Webhooks
Active Directory and LDAP
Datadog and Splunk
OpenAI, Anthropic and Ollama

FlowForge holds no certification. Its role controls and audit ledger produce records your own compliance work can use.

Rudratic Technologies Ltd · London and Chennai · info@rudratic.com · rudratic.com/products/flowforge

FlowForge datasheetPage 2 of 2