An honest status
A status is derived from what is actually deployed and what a project’s own documentation says. A prebuild probe records what each launch link returns, and a successful page load alone never upgrades a status.
About
Dotcoder is a software studio in Los Angeles. It builds and operates its own platforms, apps, and games, runs two operating companies, JoinLinks and EnetixData, and delivers client work with the same practice.
Four product families share one collection. JoinLinks is a social and entertainment events platform for Black Los Angeles. EnetixData is a family of data and analytics platforms: crypto intelligence, portfolios, backtesting, prediction, and dashboards. The platforms family holds self-hosted AI tooling, agent environments, operator software, and everyday apps. The games family holds browser-first worlds and native prototypes.
Client engagements are the same practice, pointed at someone else’s product: a written scope, short review points, and evidence for each delivery. The service outlines describe what that covers and how an engagement starts.
Four practices
Work is planned as short sprints and delivered by coding agents running on the studio’s own machines. Four rules decide what that means in practice.
A status is derived from what is actually deployed and what a project’s own documentation says. A prebuild probe records what each launch link returns, and a successful page load alone never upgrades a status.
Coding agents do the building. People own scope, review, and every production approval, on the studio’s own projects and on client work alike.
The tooling the studio runs on is built to live on infrastructure its operator controls: a self-hosted assistant, a reviewer that reads snapshots instead of running code, an agent environment whose Mac stays authoritative, and self-hosted build runners.
Work is planned as short sprints with review points. Each delivery hands over the source changes, the build, test, or browser evidence behind them, and a short note on what remains.
Every sprint, on studio projects and client work alike, runs the same four steps.
Built here, used here
The tooling that makes agent-driven delivery possible is part of the collection, with the same honest status as everything else.
An AI assistant you can use across devices, running on infrastructure you control.
A pull-request review platform that reads frozen snapshots as data and never executes or pushes code.
Work with your coding agents from any device while your projects run on your own Mac.
Keep an eye on your development machines, workloads, and fleet health from one companion app.
Builds, tests, and simulators run on machines the studio owns rather than on rented runners. Apple silicon Mac Studios and a Mac mini carry macOS and iOS builds, test suites, and simulator work; Linux workstations with GPUs carry GPU work; a Windows workstation carries Windows continuous integration. Dotcoder Fleet is the control plane that keeps an inventory of them.
Machine classes and roles are all that is published here: no hostnames, addresses, accounts, or network details.
Every project is one dot. Colour is the product family; fill is the status. The same three glyphs appear on every card, profile, and ledger on this site.
Released and reachable at its own link. Several live projects sit behind the Alpha password until their public release; the card and the profile say so.
A preview, prototype, or MVP, sometimes gated or sign-in only. Usable, but not finished.
Still being built, or a private engineering environment that is not distributed.
Launch links last checked October 26, 2026.
Dated and sourced
Launches and status changes on this site and in the collection. Each entry is dated by the commit that made the change.
JoinLinks moved from preview to live on the ledger: make friends, join communities, host Links and ticketed events, and follow an event feed for Black Los Angeles at joinlinks.com.
A prebuild probe records what each project’s production link actually returns, so a status on this site reflects the last check rather than an intention.
This site gained a Windows continuous-integration job on Dotcoder Fleet, alongside the existing macOS and Linux runners.
The public tier gained in-depth family pages for JoinLinks and EnetixData and a generated social card for each public page.
A public profile for every platform, app, game, and service came out from behind the Alpha password. Guides and launch links stayed with members.
The studio landing page was published without a password, separating the public company site from the members’ collection.
Explore is open to everyone: a profile for every platform, app, game, and service, with its current status and, where a project is live, its own front door. The signed-in collection adds getting-started guides, current access paths, and first-session walkthroughs, and is where the products themselves are opened.
The collection is in Alpha: sign-in asks for the shared Alpha password, then Dotcoder Hub membership. Developer operators use a separate GitHub-authenticated hub.
Asked most often
Alpha is the state of the members’ collection. Signing in asks for the shared Alpha password first, then Dotcoder Hub membership. The public Explore tier, with a profile for every project, needs neither.
The live ones, yes. A live project is opened either from its own launch link or from the members’ collection; a preview or a private engineering environment is not open yet. Each profile states where its project stands.
Both are operating companies, built and run by the studio, and each is one of the four families in the collection. JoinLinks helps people make friends, join communities, and find social events in Black Los Angeles, on iOS, Android, and the web. EnetixData is a family of data and analytics platforms. Each keeps its own identity system and its own terms inside its products.
From what is actually deployed and what the project’s own documentation says. A prebuild probe records what each launch link returned at the last check, and a successful page load alone never upgrades a status.
By email to dev@dotcoder.info. An engagement starts with a written scope: the product goal, the current state, and what a useful first outcome looks like. Access to repositories or environments comes only after the scope calls for it.
Every project with its status, family, and front door.
What an engagement covers, and how one starts.
One address for client work, access, press, or a correction.
Already a member?Sign in to the collection