Is Mirabilis a consulting company or a software company?
Mirabilis is a software company. Engagements include VisualSim licenses, system-level modeling, and risk analysis to accelerate adoption. The goal is to transfer capability, not create long-term dependency.
What does a typical Mirabilis engagement look like?
We start from your architecture specifications and constraints, assemble a system-level model, explore thousands of what-if scenarios, quantify architectural risk, and deliver decision-grade insights. Software licenses are included, and your team takes ownership at the end.
Do you build the models for us?
Yes. We assemble the initial system model based on your specifications, assumptions, and workloads. This ensures correctness and speed early on, while your architects and performance engineers learn how to extend and maintain the model.
What happens after the engagement ends?
Your team retains the VisualSim licenses, models, and methodology. We transfer knowledge so your architects and performance engineers can continue exploring architectures, validating assumptions, and managing risk independently.
What kind of results do customers see?
Customers use Mirabilis to:
- Identify high-risk architectural assumptions early
- Avoid over- or under-provisioning
- Reduce late-stage surprises and rework
- Focus verification where it matters most
- Enter implementation with validated system specifications
The impact is measured in time saved, risk avoided, and cost prevented.
How is Mirabilis different from traditional EDA tools like Synopsys Platform Architect?
Traditional EDA focuses on implementation correctness once an architecture is largely fixed. Mirabilis focuses on architectural risk mitigation early — quantifying how wrong a decision could be, where the system breaks, and what the consequences are. The two are complementary, not redundant.
How does Mirabilis compare to network or protocol simulators like OMNeT++ or ns-2?
Those tools are excellent for detailed protocol or network behavior. Mirabilis models the entire system — compute, memory, interconnect, software, workloads, power, and constraints — to answer architecture-level risk and trade-off questions they are not designed to address.
Why not use open-source discrete-event simulators like SystemC?
SystemC provides a language, not a solution. Teams must build everything themselves, often without probabilistic analysis, reusable system components, or decision-grade reporting. Mirabilis provides a production-ready platform, extensive libraries, and risk-focused analysis that teams can use immediately.
Who typically uses Mirabilis inside an organization?
Mirabilis is used collaboratively by:
- Architects defining system structure
- Performance engineers exploring trade-offs
- Verification teams identifying hotspots
- Engineering leadership evaluating risk
The output is designed to support executive-level decisions, not just technical exploration.
At what stage of the program should Mirabilis be used?
Mirabilis delivers the most value before major commitments are locked — early architecture definition, pre-tape-out, or pre-infrastructure procurement. It can also be used continuously to manage risk as requirements and workloads evolve.
