I built B.A.S.E. (Backend Automation & Scripting Environment) because I was tired of the ceremony required to deploy simple backend scripts. I wanted something that didn't require managing node_modules, virtualenvs, or container layers just to run a webhook or a daily cron job.
B.A.S.E. is a standalone language interpreted by a single 22MB binary (built in Go). You just download the binary and run your code. It’s designed specifically for backend automation and infrastructure tasks.
What’s inside:
Zero Dependencies: No npm, no pip. Just the binary.
Built-in Web Server: Static file hosting and API routing in a few lines.
Native DB Support: Direct bindings for SQLite, Postgres, MySQL, and MongoDB.
Automation First: Built-in cron-style scheduling.
Modern Concurrency: Uses Go channels and waitgroups natively (spawn, chan).
Standard Library: Includes everything from AES encryption and Discord webhooks to CSV/YAML parsing.
Technical bits: The language uses a JS/C-inspired syntax. Under the hood, the interpreter handles an "Auto Keep-Alive" system - if you start a server or a scheduled task, the engine stays alive without you needing to write infinite loops.
I’m currently using it for my own homelab automation and for building lightweight APIs.
I’d love to hear your feedback on the DSL design and the "single binary" approach for this kind of work.
igorkalen•2h ago
I built B.A.S.E. (Backend Automation & Scripting Environment) because I was tired of the ceremony required to deploy simple backend scripts. I wanted something that didn't require managing node_modules, virtualenvs, or container layers just to run a webhook or a daily cron job.
B.A.S.E. is a standalone language interpreted by a single 22MB binary (built in Go). You just download the binary and run your code. It’s designed specifically for backend automation and infrastructure tasks.
What’s inside:
Zero Dependencies: No npm, no pip. Just the binary. Built-in Web Server: Static file hosting and API routing in a few lines. Native DB Support: Direct bindings for SQLite, Postgres, MySQL, and MongoDB. Automation First: Built-in cron-style scheduling. Modern Concurrency: Uses Go channels and waitgroups natively (spawn, chan). Standard Library: Includes everything from AES encryption and Discord webhooks to CSV/YAML parsing. Technical bits: The language uses a JS/C-inspired syntax. Under the hood, the interpreter handles an "Auto Keep-Alive" system - if you start a server or a scheduled task, the engine stays alive without you needing to write infinite loops.
I’m currently using it for my own homelab automation and for building lightweight APIs.
I’d love to hear your feedback on the DSL design and the "single binary" approach for this kind of work.
Repo: https://github.com/igorkalen/base Thanks! Igor