Welcome to Nutdat, a personal experiment and long-term vision to build my own complete development platform — starting with the tiniest building blocks.

This project is about writing and structuring all my own little packages (called nuts) and exploring just how far I can go by building everything myself. Each nut is a standalone repository (e.g. Nutdat/config) — modular, focused, and hackable.

Imagine this:

You install a single Go binary on a root server, and instantly get a self-hosted IDE with everything you need to build, test, deploy, and manage modern web apps — entirely on your own stack.

This includes:

• Your own Git system
• Your own CI/CD pipeline
• Your own backend & frontend framework
• Your own development interface, fully integrated and pre-configured

All of this is composed from tiny modules — nuts — and blueprints for them — nests.

A nut is a small, focused Go module or service — a tiny building block for the larger system. Each nut lives in its own repository and serves a single purpose:

• config → config loading & environment handling
• log → structured logging
• web → minimal HTTP server
• auth → authentication primitives
• ...and so on

They’re designed to be combined into something bigger, but still useful and understandable on their own.

A nest is like a template or scaffold — a predefined setup composed of multiple nuts. You could think of it like:

• A full-featured backend service scaffold
• A boilerplate web app
• A Git-backed deployable site generator

Nests help bring structure and reuse without hiding how things work.

The final form of this project is a fully self-contained development environment that you can spin up on your own server and immediately:

• Write and run code
• Use your own Git & versioning system
• Build and deploy apps
• Plug in nuts (modules) and nests (templates)
• Extend it with your own ideas

All designed to run from a single binary you control.

Right now, this is a living and evolving experiment. It’s not a product, it’s not a framework — it’s a process.

• ✅ Publishing core nuts in separate repos
• 🧪 Experimenting with tooling
• 🛠 Planning out the larger architecture
• 🚀 Working toward a first local prototype

• To learn and understand every part of the stack
• To avoid vendor lock-in
• To build something that’s truly mine
• To share the process and inspire others who want to go deep

Thanks for checking this out. If you're curious, feel free to explore the other Nutdat repositories and follow the journey.

Not a framework. Not a startup. Just a nutcase building their own tools.