Most automation platforms today are cloud-first: your workflows, credentials, and data all live on someone else's servers. Nodlyn takes the opposite approach — everything runs locally on your machine.
The Problem with Cloud-First Automation
When you connect your Gmail, database, or internal API to a cloud automation platform, you're sending credentials and data through a third party. Even with encryption, you're trusting their infrastructure, their employees, and their security practices.
For personal projects, this might be acceptable. For businesses handling customer data, financial records, or proprietary information, it's a non-starter.
What Local-First Means
With Nodlyn, your workflows execute on your hardware. Credentials are stored in an encrypted local vault (AES-256). Data never leaves your machine unless you explicitly configure an outbound connection.
- Zero telemetry — Nodlyn doesn't phone home. No usage analytics, no crash reports sent without your consent.
- Works offline — Build and run workflows without an internet connection.
- You own your data — Export workflows as JSON. No vendor lock-in.
When Cloud Makes Sense
Nodlyn isn't anti-cloud. Our optional Cloud Sync lets you back up workflows and run them on a remote server when you need 24/7 uptime. But the choice is always yours — cloud is an add-on, not a requirement.
The Bottom Line
Local-first isn't a limitation — it's a feature. You get faster execution (no network latency), complete privacy, and full control. That's the Nodlyn philosophy.