Developer products that do the work.
Trusplex Console is where the Trusplex products live. Operator, Dispatcher and Spotter each take a job off your hands, and they share one sign-in, one set of projects and one place to decide who may do what.
Each one is named for what it does.
Operator operates. Dispatcher dispatches. Spotter spots. Open any of them from a project, and turn on only the ones you need.
Operator runs the server work you'd rather not.
An ops agent on your servers over SSH, with a live terminal, files and write-only secrets beside it. It asks before anything destructive, and records everything.
Trusplex OperatorDispatcherDispatcher routes every ticket to its fix.
Tickets arrive from people, your systems, GitHub and Jira. Dispatcher triages each one for priority, type and danger, and hands the safe, actionable ones to an agent.
Trusplex DispatcherSpotterSpotter watches your site for what went wrong.
Issue reports with the screenshot, replay, console and network attached, flags your code raises, and cookieless web analytics, from one script on your site.
Trusplex SpotterOne project for each thing you ship.
A project is one app, site or service. Its servers, issue reports, tickets and connections all live in it. Name it, and everything else comes after.
Environments, when you need them
A project starts with one environment, and that is all most projects need. Add another, such as staging, when you want to try changes apart from production. Each environment keeps its own servers, sites, tickets and settings.
Your organization, your members
Invite people by email. Someone who has signed in before joins at once; anyone else joins the first time they sign in with that address. Belong to several organizations and switch between them.
Access you grant on purpose
A grant at the organization covers every project. A grant at a project or an environment stays there. Revoking access takes effect immediately.
A JSON API behind every page
Every product answers /api/<product> with the same checks the pages use. Name the project in x-tpx-project and, optionally, the environment in x-tpx-environment.
Four roles to start from.
Every member gets a role, and you can grant more on top of it. The last owner of an organization can never be removed.
- Owner
- Everything, including what is added later.
- Admin
- Everything except destructive actions and revealing secrets.
- Member
- Every read, plus day-to-day product actions. On Operator, that means the agent. The terminal, files, commands and secrets are granted to a person deliberately.
- Viewer
- Read-only.
Destructive actions, such as restarting a server, deleting files or deleting a project, re-check your permission at the moment they run, without relying on a cache.
Connect a provider once. Every product can use it, and none can read it.
Connections holds your credentials for the services the products work through. A product asks for a capability, such as "a language model" or "a webhook", and never sees the key behind it.
- Language models
- OpenAI, OpenRouter or Ollama: the model behind Operator's agent. You choose the connection per environment.
- Agent routines
- Claude Code routines on an Anthropic subscription, fired by Dispatcher to resolve tickets. Runs count against that subscription, not API credit.
- Webhooks
- Signed events to any HTTPS endpoint, for Dispatcher's resolution targets and Spotter's hooks and routing rules.
- Also connectable
- Cloudflare, GitHub, Amazon S3, Linear and Resend.
Write-only credentials
A value is posted once and encrypted with AES-256-GCM. Afterwards the console shows only whether it is set and its last four characters.
One connection, many environments
Override a connection per project or per environment. Each value is marked "overridden" or "inherited", and promoting one environment's values to another shows you the diff first.
Start with one project.
Sign in and name your first project. The project home lists every product with where it stands and the next step, so a new project reads like a checklist.