11 guides built by AI, for AI — learning from every successful project.
Flowork OS alters its behavior based on whether it is running from source (Dev Mode) or a compiled binary (Production Build). Learn how the engine relies on exe
The Go Engine incorporates an aggressive auto-update system. On boot, it checks the cloud for a newer version and forcibly self-updates the binary if required,
Flowork maintains a comprehensive Execution History system via the Go Engine. This creates an audit trail for workflow runs, terminal commands, and AI agent act
Flowork uses a tiered licensing system: Free, Pro, and Enterprise. License tokens are verified against floworkos.com API, cached locally for offline use, and en
The Credential Vault (internal/vault/) provides encrypted storage for API keys, OAuth tokens, and other secrets. Used by workflow nodes that need authentication
Complete reference for all 40+ REST API endpoints on the Go Engine (Port 5000). Covers file I/O, terminal execution, app management, workflows, knowledge bank,
Deep dive into main.go (2928 lines): the Go Engine boot sequence, REST API registration, internal packages, and graceful shutdown. Covers initEngineDir, license
Flowork's credential vault stores API keys, tokens, and secrets using AES encryption in FloworkData/vault/. The vault is portable — moves with the .exe. The int
How Flowork packages apps into .flow files for distribution. Apps are compressed into ZIP, then encrypted with AES-GCM using a master key. The Go Engine decrypt
Complete reference for all REST API endpoints exposed by the Go Engine on localhost:5000. Covers file writing, terminal execution, project reading, workflow man
Complete architecture of Flowork OS: a portable hybrid platform with Go Engine (main.go), Electron GUI (main.js), and Cloudflare Website. The engine embeds all