erlc global
bashe

bashe

Developer · Builder of M3
connecting…

Wrote M3 Manager from scratch. Sold the project to ERLC Global in 2026; still around as the developer.

~/work/bashe
$whoami bashe — developer, builder, shipper $cat skills.json {   "primary": ["Node.js""Electron"],   "also":    ["Python"],   "general": "yeah, that too" } $
Node.js Electron Python JavaScript general  ¯\_(ツ)_/¯
work

M3 Manager.

My main shipped product. Multi-server alt-account manager — bot launching, cookie analytics, real-time monitoring. Now part of Alting Central under ERLC Global.

M3 Manager

v1.2.0 · electron + node

Desktop alt-account manager. Built solo. Sold to ERLC Global on 2026-04-30. Still maintained.

See M3

Alting Central

collab · network ops

M3 ships into the Alting Central network. 13 servers, the alt-tooling backbone for ERLC.

Browse network

More inbound

tba · open

Whatever the next thing is — node, electron, glue scripts. DM if you've got an idea worth shipping.

From solo project to network.

Built M3 because the existing alt-account managers were either expensive, unreliable, or both. Wanted something that just worked — multi-server, cookie analytics, lifetime keys, no subscription nonsense.

Shipped solo through v1.2.0. Around then, Jay at ERLC Global reached out about acquiring it. Sold the product on April 30, 2026 — kept the dev seat. They handle distribution, infra, and Alting Central network ops. I keep coding the thing that runs underneath.

Best of both worlds: build the tool, let someone else handle the rest.

What I reach for.

Runtime
Node.js
Desktop
Electron
Scripting
Python
Frontend
Vanilla JS · HTML · CSS
Auth flows
OAuth · cookie systems
Data
SQLite · JSON
Ops
Git · CLI
Other
general  ¯\_(ツ)_/¯

Talk to me.

Best path is Discord — find me through any of the M3 / Alting Central servers. Or message Jay.