Friction eliminated, not rigor
The model underneath is formally correct and designed to map cleanly onto standard interchange formats. What we removed is the dialog maze, not the engineering.
About
Built by a systems engineer who wanted this to exist
Prometheus SE started from a straightforward frustration: the tools capable of doing real systems modeling are almost impossible for an individual engineer to actually get hold of and use.
Why it exists
Capability is not the problem. Access is.
Established MBSE tools are genuinely powerful. They are also delivered through enterprise procurement, gated behind license servers and IT approval, and built on a specification you are expected to learn before you can be productive. If your employer has not bought you a seat — or you do not have an employer — that capability is simply not available to you.
The result is that most engineered systems are never formally modeled. The knowledge lives in a slide deck, a spreadsheet and somebody's memory, and it degrades from the day it is written. Prometheus SE exists to make the formal model the easy path instead of the expensive one.
The name is not decoration. Prometheus stole fire from the gods and gave it to the people who needed it. That is the whole thesis: real capability, handed to the practitioner, without asking anyone's permission.
The governing principle
The Complexity Budget
Every proposed capability has to pass the same test before it is built at all: does this serve the practicing engineer, or does it exist only because a traditional MBSE tool has an equivalent? "The standard has a concept for this" is explicitly disqualified as a reason on its own.
This is not minimalism for its own sake. Capability under the hood is roughly on par with traditional tooling — the model is real and rigorous. The budget exists to stop the product slowly re-accumulating the exact complexity that made those tools inaccessible in the first place.
No IT, no procurement, no license server
It runs in the browser. There is nothing to install, nothing to approve, and no seat to be allocated to you by somebody else.
Every capability earns its place
A feature existing in a traditional MBSE tool is explicitly not a reason to build it here. If it does not serve the practicing engineer, it does not ship.
Domain agnostic
Industrial machinery, building systems, consumer products, medical devices, energy infrastructure — any engineered system you need to formally document.
Who it's for
Three people, one model
Modeling engineers
Systems engineers, product engineers, technical writers and students who understand systems thinking but have been priced out or complexity-locked out of traditional MBSE tooling.
Inheriting engineers
Anyone handed a system with a partial model, or none at all — with a stack of datasheets and manuals where the documentation should be.
Diagnostic users
Technicians, test engineers and field service staff troubleshooting a real unit. No modeling background needed; describe the symptom in plain language.
The company
Who is behind it
Prometheus SE is a product of Tactical Partnering Solutions LLC. It is being built deliberately and in the open with a small group of beta engineers, rather than launched loudly and fixed later.
Questions? info@prometheus-se.com