I’m working on [Homestead](https://myhomestead.dev), which is my OSS solution for building personal apps. You can build web-apps and Homestead will handle backend, agent support, authentication, notifications, and a bunch of other stuff.
I’ve used it to build a grocery store list, credit card perk tracker, address book, mini-golf scorecard app, and a bunch more. It’s really helped having all of the “platform” stuff handled for me so I can just focus on the app.
I’ve been working on an OSS backend-in-a-box called [aepbase](https://aepbase.io/).
For the past few years, a group of us from Google, Microsoft, GM, IBM, Roblox, Rubrik + more have been working on a design standard for APIs called [AEP](https://www.aep.dev). The goal is twofold: learn from our companies mistakes around APIs and enable better tooling with less configuration.
We’re at a point where AEP-compliant APIs get a resource-oriented CLI, MCP server, full UI, and Terraform provider for near-zero configuration.
Aepbase has been my way to tie the whole ecosystem together. You run a single binary and define the schema for a resource with one API call. Now, you’ve got a full set of CRUD APIs and support for CLI/TF/MCP/UI. After one API call.
It’s a really cool way to tie together all of the work AEP has been doing.
Love to hear HN’s opinions on all of this. We’re still trying to figure out the best way to sell people on AEP.
The AEPs were originally based off Google AIPs, but we did a hard fork and have altered a lot since then. For one thing, the AIPs were entirely protobuf focused, while we're focusing equally on protobuf + OpenAPI.
The CRUD methods are great examples where we deviate from the AIPs.
I’ve used it to build a grocery store list, credit card perk tracker, address book, mini-golf scorecard app, and a bunch more. It’s really helped having all of the “platform” stuff handled for me so I can just focus on the app.