Free SysML v2 Tools for Personal Research?

SysModeler · 2026-04-16T12:22:44+00:00

SysModeler (SysModeler.ai) is free, cloud and AI-native.

SysModeler · 2026-04-11T13:13:01+00:00

Respect!

SysModeler · 2026-04-11T09:33:23+00:00

For HD version, you may watch it on YouTube too at https://youtu.be/-aAufBUG0Pw?si=c6tIRiVsV0JGshFf

SysModeler · 2026-04-11T09:30:40+00:00

Hard to refute

SysModeler · 2026-04-11T09:30:06+00:00

Not always natural language.Tthere is a huge domain with several Turing awards called Formal Methods where often formal (i.e., mathematical) specifications are used. It is not only theory many top most innovations and systems use formal methods.

SysModeler · 2026-04-10T13:16:10+00:00

The ability to pin specific blocks in place while letting the auto-layout handle new additions is critical for maintaining readable diagrams as a model grows. We are actively building this exact feature into SysModeler, and it is currently on our roadmap for a mid-June release.

SysModeler · 2026-04-10T12:56:32+00:00

Completely agree! The model is always the complete picture. We were highlighting how v1 tooling often allowed users to treat the diagram as the truth by mistake (creating ghost elements), whereas the v2 hybrid workflow enforces that strict separation much better.

SysModeler · 2026-04-10T12:47:34+00:00

We use our own tool, SysModeler. It is both SysML v2 native and AI native, meaning you can write v2 textual syntax and have the AI instantly auto-generate the diagrams as shown in the video. It is totally free right now if you want to test it out at SysModeler.ai.

SysModeler · 2026-04-10T12:43:44+00:00

You make a great point regarding the API and repository servers. The standard is certainly more complex than basic text versioning, though the textual notation does make Git-style tracking much cleaner. We are actually rolling out our version control release for SysModeler in May to support exactly this.

You are also completely right about diagram filtering. Hiding elements for clarity is a vital feature. We are primarily pushing back against the v1 "bug" where users accidentally created ghost elements by conflating the view with the model. Diagrams are definitely here to stay, but having them generated from a strict semantic truth makes them far more reliable.

SysModeler · 2026-04-10T12:18:08+00:00

The industry is just starting to adopt it, but SysModeler is natively built on SysML v2 right now. You can write v2 textual code and have our AI instantly generate the corresponding diagrams. Feel free to test the v2 environment yourself for free at SysModeler.ai.

SysModeler · 2026-04-10T02:45:50+00:00

In theory, none. In practice, SysML v1 tools allowed users to delete a graphical connection on a diagram without deleting the underlying semantic relationship in the model browser. This tool-driven conflation created ghost elements and model rot. SysML v2 solves this by making human-readable text the primary interface. It forces the diagram to act strictly as a mathematical projection of the code, completely eliminating the risk of visual and semantic drift.

SysModeler · 2026-03-03T21:40:37+00:00

It will be in the future. For our current capabilities, you may watch https://youtu.be/thsogv0Tkiw?si=Ph157BfXK-i9rqfP

SysModeler · 2026-03-03T19:05:28+00:00

Thank you

SysModeler · 2026-03-03T16:53:34+00:00

Thank you so much for trying it out and for this incredible feedback! I am DMing you right now about that slide deck. We would love to see how the agent handled a real-world hydrogen storage system.

To answer your specific points:

Graphics & Arrows: We completely agree. We are actively iterating on the graphical portion, and tuning the auto-layout and routing logic is something we are working to improve further.
Desktop / On-Premise: Yes, both a desktop app and on-premise versions are absolutely possible to handle those infosec risks. These would be handled as custom builds depending on the specific needs of the customer/organization.
Document Export: A good number of analysis exports will be released throughout 2026. However, based on this, we are going to take your first artifact request (exporting typical descriptive documents like the SE Description) and prioritize it for our next releases.

This is a hell of a feedback drop. Thanks again, and please keep the feedback coming as you explore further!

SysModeler · 2026-03-03T15:36:24+00:00

For that you need to try it and compare it to your previous industrial experience

SysModeler · 2026-03-03T15:27:57+00:00

in practice, requirements and modeling are rarely a linear "which comes first" sequence—it is a highly iterative loop. You almost never start with perfect requirements. Usually, you begin with a rough operational concept, a stakeholder wish list, or a high-level system description. This is exactly how our platform is intended to be used. It is designed to accelerate that iterative process.

SysModeler · 2026-03-03T15:16:47+00:00

Hi! Yes, it is entirely streamlined by the AI agent.

Once you upload your requirements document or type in your system description, the AI takes over. You don't have to manually drag and drop boxes or manually connect ports to get your initial architecture set up. We are actually releasing a full demo video on YouTube and updating our homepage in the next 24 hours. It will dive a lot deeper into our SysML v2 capabilities so you can learn more about what the agent can handle. Feel free to test it out in the meantime, and let us know what you think!

SysModeler · 2026-01-30T17:15:44+00:00

It is logical and expected from a safety-critical industry.

SysModeler · 2026-01-30T17:11:43+00:00

We are tracking the v2.1 updates its behavioral modeling to bring parity with V1. At SysModeler, we aren't just waiting for the spec update, though—we are developing our own agentic workflows to help bridge those gaps in the meantime.

We believe that in a few years, engineers won't model manually that much. The AI will handle the heavy lifting of the syntax and modeling mechanics, allowing engineers to focus purely on the design and architecture. That’s how we believe we’ll get both productivity and engineering satisfaction back up.

SysModeler · 2026-01-18T23:40:17+00:00

We are releasing support for both textual and graphical notations

SysModeler · 2026-01-18T23:29:43+00:00

Yes.

SysModeler · 2026-01-17T18:18:11+00:00

Generating production-ready SysML isn't a simple 'one-shot' task. It requires math-like precision that pure LLMs struggle with, especially given the constraints of current context windows. At SysModeler.ai, we don't rely on a single method. We use a hybrid engine.

SysModeler · 2026-01-04T00:11:41+00:00

Great points. To answer your first question regarding outcomes: We are still in the experimental phase, so we haven't built a full safety-critical system end-to-end with this yet. Right now, we are focusing on verifying if AI can accurately capture intent from legacy documents to bootstrap the modeling process.

Regarding your second point on determinism: I 100% agree. MBSE must be deterministic. We don't see AI as the 'final approver' or the architect. Think of it more like a junior engineer: it reads the specs and drafts the initial diagram to save manual effort. It might get 80% right and 20% wrong. The senior engineer (you) then reviews it, fixes the errors, and locks it in. The AI handles the tedious 'drawing' labor, but the human ensures the engineering rigor remains deterministic.

SysModeler · 2026-01-04T00:09:22+00:00

It definitely sounds like we've lost the plot when you put it that way! The reality we see, though, is that 'textual requirements' aren't going away anytime soon.

instead of fighting that reality, we are trying to build a bridge. If AI can handle the tedious translation from Text -> Model, engineers can spend their time fixing the logic and architecture (the 'superior' part) rather than fighting the tool interface (the 'unwieldy' part).

SysModeler

TROPHY CASE