We have put @zeitwork on hold. The chance of us continuing it has become rather low as all the original co-founders have pivoted to something else that they're currently working on in stealth. We still believe in Zeitwork and that the world needs better ways to build, deploy, scale your apps. It was not an easy decision for all of us. Looking forward, the good news is that we all can now go full-time on what is next :)

we're hosting the zeitwork web app on zeitwork infra btw

decided to record a 3-minute walkthrough of @zeitwork today

What frameworks should @zeitwork support out of the box?

at @zeitwork we are building a platform to deploy *any* app you know how good Vercel's UX is? now imagine that for *everything*: backends, AI agents, Rails apps, voice AI, full-stack monoliths. zero constraints fully open source. DM for early access

time to move everything to @zeitwork

spinning up test envs to start stress testing before we launch

I think we’re getting close to stress test the new architecture. This means we’re getting closer to a launch

working on @zeitwork (coss) to make it easy to launch without the limitations of traditional cloud what if I take care of the hetzner vps and give you the easy of 1. connect your repo 2. we deploy and scale it globally at incredible cost we bring the bare metal servers

yesterday, we had a design session with @aaronmahlke and @arronflashman and came up with this gorgeous yet familiar navigation