EZConfig

You built something with AI. Now what?

120+ ways to get your tools to other people — explained in plain English, with copy-paste prompts for any AI tool. Or just pick a card, point your agent to this URL, and ask it to walk you through a specific configuration and deployment.

Find Your Vehicle

Answer 3 quick questions and we'll narrow it down for you.

What did you build?

What do you want to do with it?

How much complexity are you comfortable with?

Here's what we'd recommend

Full Catalog

How I Got Here

I'm a lawyer who peaked as a programmer in 2019 when I took a free Python course on Codecademy and built a tiny dispute resolution tool as an exercise.

Fast forward a few years and suddenly AI can write code for me while I point and say "no, more like this" until something works. I started building tools — little things at first, then bigger things. But I kept hitting the same wall: I'd build something on my laptop and then have no idea how to get it to anyone else.

The first unlock came from a coworker who said "just put it in a GitHub repo and deploy to Pages." I didn't know what that meant, but I tried it, and suddenly my little tools had URLs. I started ending my AI prompts with "and put it in a Pages web app and deploy it." It worked. I was dangerous.

Then I built a hockey shot tracker. I'm a hockey parent — my son plays in a youth league, and the coaches were tracking shots on paper. I vibe-coded a simple web app where you tap on a rink diagram and it records where the shots came from. The team started using it. Then other coaches in the league started using it. It was the most rewarding thing I'd built, because people who weren't humoring me were actually choosing to use it.

But it was a static site. Data lived in the browser. Close the tab, lose your games. I wanted real accounts, real data persistence, season-long analytics. I was telling a coworker about it and he said: "Set up a free Neon database and hook it up to free Vercel hosting." I didn't know what either of those things were. But I tried it, and it worked, and suddenly I had a real app with a real database and real user accounts, running for free. That was the real unlock.

The code would make an actual engineer cry. The coaches don't care.

Every single vehicle I discovered was because someone happened to mention it. "Have you tried a menubar app?" "You know you can make a Chrome extension, right?" "That could be a PWA." Each time, a door I didn't know existed swung open.

That's why this project exists. Not everyone has a coworker who happens to know about Vercel, or menubar apps, or that you can compress an entire app into a URL. EZConfig is the coworker. It's every door I've found (and a lot of doors other people have found), listed in plain English, with a prompt you can paste into whatever AI tool you use to walk through it.

I can't write code. But I can tell you what it felt like to not know these things existed, and how much changed each time I found out.

github.com/dvelton