TypeScript-First Framework Aims to End Serverless Cloud Lock-In
I just pushed out serverless/Cloudflare support for Vramework.dev! The goal is to let you write business logic once and deploy it anywhere—AWS, Azure, on-prem—without having to rewrite huge chunks of your codebase when you switch infrastructure.
What is vramework?
It isn't another server, but rather a normalization layer ontop of the many serverless and server frameworks available today.
What’s new?
Serverless support now includes HTTP, WebSockets, and scheduled tasks (cron jobs). You can still run Vramework on regular servers (Express, uws, Fastify, ws) as simple middleware.
Why?
Avoid Lock-In: Early hosting decisions can be painful (and expensive) to change later. Specially when serverless. Cost Control: Switch to a cheaper platform if, for example, egress fees on AWS get out of hand. Enterprise On-Prem: Easily move on-prem for customers with compliance or policy constraints. TypeScript-First: Built around TS from the start, so it feels natural for modern JavaScript teams. Developer Experience: By analyzing code in a compile step, Vramework can generate OpenAPI docs, typed fetch clients, and typed WebSocket clients automatically. Better development experience: Run/Test your functions locally via express/uws for quicker interation
I’m now working on a smarter dependency injection system that figures out which services each function needs—further reducing cost and complexity. This will slow down feature releases while I improve documentation and explain why this model matters.
I’m also looking for a new job or an interesting project/team to collaborate with, so if you have any ideas or opportunities, feel free to reach out!
Check it out and let me know what you think — feedback and questions welcome.
Thanks, and happy holidays!