Online from Zac's desk

Zac Batten / Inefy

I build small internet machines: Twitch tools, movie-night bots, GitHub Pages experiments, and helper scripts that turn recurring annoyances into buttons.

Stream tools Field ops Static web Small automations
Open the workbench GitHub
$ now tuning MovieBot, polishing the site, and catching the next tiny automation idea
0 active project lanes
OBS stream tools in orbit
Pages static, fast, easy to remix
Inefy the handle on the toolbox
TraverseOps Municipal field maps MovieBot OBS handoffs GitHub Pages Twitch chat tools Automation scraps Build notes TraverseOps Municipal field maps MovieBot OBS handoffs GitHub Pages Twitch chat tools Automation scraps Build notes

Workbench

Tools with fingerprints on them.

This is not a polished trophy case. It is the bench: finished pieces, useful half-ideas, and the little experiments that make streams and projects less repetitive.

Live site HTML / CSS / JS

zacbatten.me

The public workbench itself: a tiny static site with enough motion, attitude, and room to keep changing as the projects get sharper.

Field ops Maps / Supabase / Capacitor

TraverseOps

A municipal field workspace for finding infrastructure on a map, logging inspections, creating work orders, and keeping asset records synced.

Prototype lane Scripts / Helpers

Manual task detector

A parking spot for the next tiny tool that starts as "why am I doing this by hand again?" and ends as a command, checklist, or widget.

Open slot Next stream toy

Chat-powered side quest

A small future build for overlays, polls, scene cues, or anything that lets the audience poke the edges of the stream without derailing it.

Project Spotlight

TraverseOps turns field work into a shared map.

I built TraverseOps as a focused municipal operations app for crews who need to find assets, record what happened on site, and turn problems into trackable work without bouncing between paper notes, spreadsheets, and separate map tools.

MapLibre Supabase Offline-aware sync Capacitor shell
TraverseOps field workspace showing a municipal asset map and selected asset panel
What I Made

One operations workspace

A browser-first app that brings the asset map, registry, inspections, work orders, and reports into one field-friendly interface.

How It Is Used

Tap, update, assign

Crews search for an asset, open it from the map or list, update status, attach notes or photos, and create work orders for follow-up.

Why It Exists

Less record chasing

The goal is to keep office and field teams looking at the same operational picture instead of reconciling scattered notes later.

Build Notes

Static app, real backend

The front end is static HTML, CSS, and JavaScript, with MapLibre for mapping, Supabase for shared data, and Capacitor for native packaging.

Systems

The build loop.

The fun part is not making giant platforms. It is spotting a repeated friction point, making the smallest useful thing, and turning it into something with a little personality.

01

Catch the itch

Movie nights, stream setup, repo chores, notes that keep getting rewritten.

02

Ship the tiny version

One button, one command, one page, one bot behavior. Small enough to finish.

03

Make it feel alive

Clear labels, bright feedback, useful defaults, and just enough visual spark.

04

Leave breadcrumbs

Write down the setup details before future-Zac has to reverse engineer them.

Current rule

Make the useful version first. Make it pretty after it survives real use.

Favorite scale

Small enough to finish, annoying enough that finishing it feels great.

Why Inefy

A short handle for the experiments, repos, and tools I want under one roof.

Tiny Lab

A project seed generator for my kind of weird.

Tuned for stream helpers, practical automation, web experiments, and tools that sound small until they save a night.

> Generate a project seed when the bench needs a new spark.

Now

What has my attention.

MovieBot

Smoother movie nights

Making Twitch voting and OBS handoffs feel less like production chores and more like part of the room.

Site

A homepage that sounds like me

Keeping this page honest: fewer generic portfolio lines, more notes about the projects I actually touch.

Notes

Leaving setup trails

Writing down tradeoffs and tiny setup details before I forget why the build works the way it does.

Contact

Want to poke around?

Most of the interesting stuff lands on GitHub first. This site is the map, the notebook, and the occasional shiny button.