Erebora
Menu
MANTISDevelopment control · Windows + AndroidWorking private system · public preview in development

Software work should not stop because I leave my desk.

So I built MANTIS. It keeps long development sessions working against the real files, terminals, browsers and tests on my Windows workstation while I control those same sessions from my phone. I can switch projects, read the terminal, send instructions, stop a job and restore the same session from Android. The goal, backups, tests and recovery stay attached to the work. The workstation must remain awake and connected.

Get the first build scoped Product walkthrough Hybrid Mantis preview

Product screens

How MANTIS works.

MANTIS

  1. The Android app opens the same live work still running on the computer.
  2. Real Hybrid Mantis Active Sessions screen on Android
    Choose any live project without starting over.

Problem

Long software jobs forget the goal, skip proof, or stop when the person at the keyboard leaves.

What I built

I built the controller that keeps real workstation sessions running, routes bounded specialist work, preserves the project goal, backs up changes, tests the result, and exposes phone control.

What this means for your project

This is the development system and proof discipline behind every product on this site.

My role

I built the workstation controller, agent coordination, browser and test proof, recovery, Android app, and file transfer.

Related services

Get the repeatable bullshit off your plate.

01Connect your tools02Software for your team03Fix and finish software products

CLIENT BUILD OR REMOTE ROLE

Get the repeatable bullshit off your plate.

01ClientGet the first build scopedSend me the customer or staff job you are sick of doing by hand. I’ll tell you the smallest paid build worth making, what it must do and how we will prove it works.02Remote roleHire a Full-Stack Product EngineerThe customer does not care which part of the stack broke. I work remotely. I can trace the problem from the customer screen through the backend, data and staff tools, then prove the action where it failed.