APIs & glue
Chaining services together, poking at weird payloads, adding logging so the next person is not guessing. We learn your vendors alongside you.
Side projects, experiments, paid odd jobs
We like the messy in-between where nothing quite fits off the shelf.
Hooks between services, half-automated spreadsheets, tiny dashboards—stuff that is not glamorous but makes the day a little lighter. If that sounds like your rabbit hole, we are probably interested. No big agency pitch: just people who enjoy figuring things out and sometimes get paid for it.
Things we might help with
Not a menu with guarantees—more a sketch of what we gravitate toward. If your ask is outside this, still write; worst case we say “not us” and maybe point you somewhere.
Shop-ish / service-ish stuff
Ledgers, bookings, payouts—the boring parts where reality does not match the tutorial. We are not selling a turnkey “platform”; we might help sketch or build a slice.
AI, carefully
When a model actually saves time and the data story is okay with you, we can experiment. When it is hype, we will probably grumble and suggest a simpler fix first.
Weird one-offs
Migrations nobody documented, performance ghosts, bugs that only show up on Tuesdays. If it is odd, we are curious; if it is huge, we will be honest about pace.
How we tend to work (when it is not just a weekend rabbit hole)
Nothing fancy—just a rhythm that keeps surprises smaller than they could be.
-
1
Chat & look around
We ask naive questions, read what you have, and try to spot landmines early. Still learning your context beats pretending we already know it.
-
2
Agree on something small
A short written slice—what we would try first, what “good enough” looks like, and what we will not touch yet. Revise if it feels wrong.
-
3
Build in the open with you
Incremental commits, demos when it helps, room to change direction. No big-bang reveal at the end unless you really want that for some reason.
-
4
Handoff or hang around
Sometimes we document and wander off; sometimes we keep a light thread for tweaks. We will say which up front instead of implying forever support.
Work, licenses, and public bits
This page is mostly a postcard. Some repos are public, some are paid plugins, some never leave a private folder—that is all fine as long as everyone agrees what is what.
- Open source when it feels useful to others and we can afford the upkeep story.
- Licensed bits when someone wants updates and a shoulder to cry on across versions.
- Closed when the details are not ours to share—no drama, just boundaries.
When there is something worth showing, it will show up here or on Gitea. Until then, imagine a lot of half-finished branches and coffee.
EasyGoing Gaming (EGG) and code
EasyGoing Gaming is the name we give our homelab-shaped world: Git, boards, CI, mail—the usual self-hosted rabbit holes. If a project wants to live near that, cool; if you would rather keep everything in your cloud, also cool. No pressure to adopt our stack.
This public site sits on www; mail and other toys use their own names behind the same kind of reverse proxy we use for everything else.
Wave from the shoreline
Whatever context you have is fine—messy threads welcome. We read everything; replies might be slow when life is loud, but we are not ignoring you on purpose.
Email: contact@easygoinproductions.com
Webmail: mail.easygoinproductions.com