agents
Copilots
AI copilots for operations, cloud workflows, and private tools that live behind your central identity layer.
hunt3r.dev brings together playful public projects, sharp utility apps, and private tools that need sign-in. One brand, clear paths, no confusing subdomain sprawl.
Projects
Each project has its own role, personality, and access pattern. Some stay open for anyone to explore. Others route through identity because they work better with private context and saved state.
agents
AI copilots for operations, cloud workflows, and private tools that live behind your central identity layer.
jobs
A sharper job search space for finding roles, tracking opportunities, and generating polished applications.
stuff
Small projects with big curiosity, from flags and body systems to timelines and geography.
id
A self-hosted identity home for private subdomain apps, shared sessions, and future account controls.
Flow
The ecosystem should feel obvious. Browse here, open what you need, and only cross into sign-in when the product actually benefits from identity and saved state.
Get the lay of the land quickly, with one clear place to see what each project does and who it is for.
Open public projects directly, or route into sign-in for the apps that need identity and sessions.
Carry a clear sense of how the projects relate, instead of each subdomain feeling like its own island.
Structure
The main site should feel calm and obvious: a clear brand, a useful overview, and sensible paths into the products people actually came for.
Next
Richer project previews and screenshots
Real status signals from agents, jobs, and other tools
Deeper copy once the app lineup settles
FAQ
The homepage should make hunt3r.dev feel intentional, not improvised.
No. Public products like stuff can stay open, while more sensitive tools like copilots can route through id.hunt3r.dev.
Because the front door has a different job. It should introduce the ecosystem, point people to the right product, and keep the overall brand coherent without turning any single app into the default homepage.
Not necessarily. A focused single page works well as a front door today, and the supporting pages already make room for the site to grow when the ecosystem needs more depth.