BrokerSIM
A Dima-and-Pablo broker roleplay sim with a 2D deal desk and a Three.js warehouse you actually walk around in. One full day end-to-end is playable today.
See the project →Two people, a handful of side projects that turned into shipped products, and an unreasonable enthusiasm for getting one more thing into users' hands.
We met as students who kept ending up in the same problem sets, then kept ending up in the same side projects. EliteDevs is the umbrella we use for the work we ship together: browser extensions on the Chrome Web Store and Edge Add-ons, browser-based games and simulations, productivity tools, and the occasional weekend experiment that turns into something real.
Most of what's on this site started as us scratching our own itch. Tab Sorter Pro existed because Dima had 60 tabs open and refused to close them. Focus Blocker existed because Pablo kept getting nerd-sniped by Wikipedia at 2am. HumanDocTyper existed because watching a doc fill out at human pace is genuinely satisfying. The pattern: build the smallest version that works, ship it, then keep going if people actually use it.
We're not an agency. There's no pitch deck. If you've got something interesting you want built, talk to us - and if we're not the right fit, we'll tell you.
Real things you can install, click, or play right now.
A Dima-and-Pablo broker roleplay sim with a 2D deal desk and a Three.js warehouse you actually walk around in. One full day end-to-end is playable today.
See the project →
Cross-browser tab organizer on the Chrome Web Store and Edge Add-ons. Used in 22 countries, growing on its own.
See the project →
Chrome extension that types into Google Docs at a real human cadence - variable WPM, natural pauses, in-doc controls.
See the project →
Privacy-first distraction blocker on Chrome and Edge. Uses Declarative Net Request - no telemetry, no slowdown.
See the project →Browser memory/swap game with rounds, lives, difficulty curves, and audio. Polished enough to keep playing past the demo.
See the project →Study-efficiency app with dashboards, practice, analytics, and a support chat widget - ready to connect to real data.
See the project →A real-time multiplayer 4X space strategy game with galaxy exploration, diplomacy, markets, ship design, research, and persistent server-hosted campaigns.
See the project ->A portable, offline encryption app for a USB drive. AES-256-GCM behind an Argon2id key, cryptographically bound to the physical drive - a copy on any other disk is just noise.
See the project ->A browser city-building simulation with procedural terrain, canvas rendering, zoning, services, economy, power, water, and saved cities.
See the project ->Two of us. We split work along what we each actually enjoy doing.
Builds the things you click on. If a project has a 3D scene, a real-time loop, or a browser extension shipping to a store, that's usually me. I like figuring out the smallest version of a feature that still feels good to use.
Handles the parts you don't see - until they break, then you really notice. I lean into the systems-y problems: networking, simulation math, and the kind of backend work that has to keep running while no one's watching.
No agency-speak. The actual rhythm we fall into on most projects.
You tell us what you actually want. We tell you which parts sound easy, which parts sound hard, and whether you should be doing this at all. No proposal documents.
We build the smallest thing that proves the idea. It's often hideous. The point is you get to use it in week one and tell us what's wrong before we've committed to a design.
Once the shape is right, we make the parts you'll touch every day feel good - animations, edge cases, performance. We don't polish what no one sees.
You get the code, the deploy, and a README that someone else could pick up. If something breaks six months later, you can read the commit history and understand what we did.
The best way to know if we can build it is to ask. Worst case, we say no - usually we don't.
Drop us a message or have a look at the rest of what we've shipped.