Haki

Pushed 9 versions of a @golang backend to greyship.tech tonight and broke it on purpose: • Bad deploy? Old version keeps serving • No traffic? Pauses itself, costs $0, wakes in ~75ms • Traffic spike? Spins up another instance on its own 0 errors at 100 req/s. No Dockerfile. No YAML Beta releases Friday, and I want you to be a part of it: forms.greyship.tech

few days into building serverless infra at @greylabs_space, just shipped optimizations that cut build times (speed depends on your plan) here's what happens when you run deploy: → the cli zips your code → a microvm builds it and uploads the binary → the binary starts in its own sandbox, with its own kernel layer (gvisor) → the router wires up networking and you get a live url all in under 30 seconds for an average go app beta launches friday. if you haven't joined yet, the form is still open help us shape the future of go on the server 👇 forms.greyship.tech

Today I used 130 million tokens on @Muse spark 1.3 contributor model Cost: $1.09 Turns: 403 Subagents: 36

Really good

Hello tech twitter, I’m building native serverless infrastructure for @golang at @greylabs_space If you’re a gopher, or just learning go , say hi let’s connect 🤝❤️

Demo of scaffolding & deploying your grey services in Seconds Also I noticed that builds may be slow if done on the server so greyship now defaults to building the go binary locally before uploading it. Of course if don’t like that path you can add the flag —remote