Vis Viva Space LLC
Developing an open-source model-based systems engineering (MBSE) tool for aerospace design.
Website: https://visviva.space
Cover Block
Publicly reported
| Field | Value |
|---|---|
| Name | Vis Viva Space LLC |
| Tagline | Developing an open-source model-based systems engineering (MBSE) tool for aerospace design. |
| Headquarters | Ventura, CA, USA [sbir.gov] |
| Founded | 2025 [sbir.gov] |
| Stage | Pre-Seed |
| Business Model | Open Source / Commercial |
| Industry | Deeptech |
| Technology | Software (Non-AI) |
| Geography | North America |
| Growth Profile | Venture Scale |
| Founding Team | Co-Founders (2) |
| Funding | Undisclosed |
| Total Disclosed | $166,582 in federal award funding [sweetspot.so, 2026] |
Links
Publicly reported
- Website: https://visviva.space
- LinkedIn: https://www.linkedin.com/company/vis-viva-space
Summary and Signal
PUBLIC Vis Viva Space LLC is building open-source model-based systems engineering software for aerospace design, and it merits attention because it has already secured a federal SBIR award in its first recorded award year, an early external signal that the technical problem is real even if the company remains very small [sbir.gov] [sweetspot.so, 2026]. The company is based in Ventura, California and was founded in 2025, with public records pointing to a two-person organization at this stage [sbir.gov] [rocketreach.co].
The public record on the founding story is still thin, which is itself part of the current underwriting challenge. What can be said with confidence is that the company emerged in 2025 around a specific aerospace engineering workflow problem, according to its SBIR materials: bringing model-based systems engineering together with a design-data repository and a continuous-integration style approach to analysis models [sbir.gov].
That product angle is the most differentiated part of the story so far. According to the SBIR award description, Vis Viva Space is developing an open-source MBSE tool for aerospace engineering that applies data-oriented programming architectures to integrate and automate analysis models, while the company website describes adjacent software for mission planning and mission design intended to improve communication and iteration speed [sbir.gov] [visviva.space]. If execution matches the description, the open-source plus commercial model could give the company a lower-friction path into engineering teams that are dissatisfied with closed, fragmented toolchains, though that remains a thesis rather than a demonstrated market outcome [sbir.gov].
Team visibility is limited in public sources. The company appears to have two employees on its SBIR profile, but named founder biographies, prior operating history, and clear commercial leadership credentials are not established in the materials reviewed, so investors are largely assessing the technical thesis before they can fully assess team-market fit [sbir.gov].
Capital formation is similarly early. No confirmed venture round, lead investor, or accelerator affiliation appears in the available sources, while federal procurement databases indicate one award totaling $166,582, which is useful non-dilutive validation but not yet evidence of broader institutional backing or commercial traction [sweetspot.so, 2026]. Over the next 12 to 18 months, the key items to watch are straightforward: whether the company converts its SBIR-backed development into a usable product, whether it can show adoption beyond government-supported R&D, and whether it adds visible leadership depth around product and go-to-market [sbir.gov] [sweetspot.so, 2026].
No independent source found -- This section relies materially on company-described product claims and SBIR records, with only partial third-party corroboration on company size and award data.
Taxonomy Snapshot
| Axis | Value |
|---|---|
| Stage | Pre-Seed |
| Business Model | Open Source / Commercial |
| Industry / Vertical | Deeptech |
| Technology Type | Software (Non-AI) |
| Geography | North America |
| Growth Profile | Venture Scale |
| Founding Team | Co-Founders (2) |
| Funding | Undisclosed |
Company Overview
PUBLIC
Vis Viva Space LLC enters the record as a very early aerospace software effort, with the clearest public signal not from a launch announcement or financing event, but from federal procurement data. The company describes itself as developing an open-source model-based systems engineering, or MBSE, tool and design-data repository for aerospace engineering, and its own website says it is building software for mission planning and mission design to improve communication and iteration speed [sbir.gov] [visviva.space].
Public chronology is thin, which is itself informative at this stage. The company is identified in the structured research as founded in 2025 and based in Ventura, California, and SBIR records show 2025 as its first award year, establishing that the business was active in the federal innovation ecosystem that year [sbir.gov]. The same SBIR materials position the initial market as aerospace engineering software, with the longer-term implication that the architecture could extend into broader engineering workflows if the product matures beyond its first domain [sbir.gov].
The legal entity name is publicly visible as Vis Viva Space LLC, and the most concrete milestone on record is its 2025 SBIR activity tied to the MBSE product concept [sbir.gov]. Beyond that, there is no confirmed public evidence in the provided source set of a venture financing round, accelerator participation, or additional dated company milestones, so the company overview remains anchored to government and company-authored descriptions rather than third-party coverage [sbir.gov] [visviva.space].
No independent source found -- This section relies primarily on sbir.gov and company-authored website claims, with limited independent corroboration and sparse dated public milestones.
The Product and the Stack
MIXED
The product claim here is narrow but concrete. Vis Viva Space says it is developing an open-source model-based systems engineering, or MBSE, tool and a design-data repository for aerospace engineering [sbir.gov]. In the same SBIR award materials, the company describes an architecture that applies data-oriented programming to aerospace design and automates analysis models through a continuous-integration pipeline, which suggests a workflow product aimed at reducing handoffs between engineering models rather than a standalone point tool [sbir.gov].
The public web footprint adds one adjacent product description, but it remains high level. The company website says it is developing software for Mission Planning and Mission Design intended to improve communication and speed iteration [visviva.space]. Read conservatively, the overlap between the website language and the SBIR description points to a systems-design software layer for aerospace teams, with an emphasis on shared design data and faster model iteration, but the available sources do not document a verified demo, named integrations, or production deployments [sbir.gov] [visviva.space].
Because the evidence base is thin, the technical assessment should stay close to what is actually on record. There are no verified public job postings in the source set, so there is no support here for a stack-level inference, and there is no public basis to describe a broader roadmap beyond the current MBSE, repository, and mission-design statements [Wellfound] [AngelList]. The notable signal is not product breadth but problem selection: aerospace engineering workflows are complex, compliance-sensitive, and still fragmented across tools, which makes even a narrowly scoped integration layer potentially relevant if the company can convert research-grade software into an adopted engineering system [sbir.gov].
No independent source found -- Material product claims rely primarily on company and SBIR descriptions, with no verified public demo, customer implementation, or independent technical validation in the sources used.
The Market They Are Entering
PUBLIC
The market matters now because aerospace engineering teams are under pressure to move design cycles faster while keeping traceability across increasingly software-defined programs, and Vis Viva Space is explicitly positioning its work inside that bottleneck rather than at the consumer-facing edge of the space economy [sbir.gov].
Public evidence on market size is thin, so any sizing discussion has to stay narrow. The only directly sourced market statement is that the company's initial market is aerospace engineering software, with possible broader engineering applications [sbir.gov]. That is a useful boundary, but not a quantified TAM, SAM, or SOM. Without a named third-party market study in the source set, the safer read is qualitative: the company appears to be targeting the engineering software layer used during mission planning, mission design, and systems-definition workflows, then leaving open the possibility that the same architecture could extend into adjacent engineering domains if the tooling proves generalizable [sbir.gov; visviva.space].
A simple way to separate what is observed from what is inferred is to treat aerospace engineering software as the core market and broader engineering collaboration tooling as the adjacent one. The SBIR award language points to an MBSE tool and design-data repository for aerospace engineering, built to integrate and automate analysis models through a continuous-integration pipeline [sbir.gov]. That framing places the product closer to technical design infrastructure than to point-solution simulation software, which matters because infrastructure tools can widen their addressable use case only if they become embedded in day-to-day engineering workflow.
| Market slice | What is supported by sources | Evidence |
|---|---|---|
| Core market | Aerospace engineering software | SBIR award describes the initial market this way [sbir.gov] |
| Product wedge | MBSE tool and design-data repository | Stated in SBIR award description [sbir.gov] |
| Adjacent market | Broader engineering applications | Described as a possible extension, not an established market presence [sbir.gov] |
| Workflow context | Mission planning and mission design software | Company website language supports this narrower application layer [visviva.space] |
The table shows a company with a clearly stated beachhead but no public third-party sizing data in hand. For investors, that means the market case currently rests more on workflow pain and procurement relevance than on a quantified category map.
Demand drivers are easier to identify than market size because they are implicit in the product description itself. The cited SBIR materials describe a system meant to integrate and automate analysis models through a continuous-integration pipeline, which suggests demand from teams that want fewer handoffs between model creation, review, and iteration [sbir.gov]. In practical terms, that points to pressure for tighter configuration control, better cross-functional communication, and faster revision cycles in aerospace design programs, especially where mission architecture decisions propagate across multiple technical disciplines [sbir.gov; visviva.space].
The federal award is also a market signal in its own right, even if it is not proof of broad commercial demand. Sweetspot reports one federal award totaling $166,582 for Vis Viva Space LLC in 2025 or later, while the SBIR company profile says the company's first award year was 2025 [sweetspot.so, 2026; sbir.gov]. That amount is small in venture terms, but it indicates at least one government buyer found the problem important enough to fund, which is often how specialized aerospace software companies begin to validate use cases before broader enterprise adoption.
Regulatory and macro forces are present here mostly through procurement structure rather than explicit rule changes in the source set. SBIR funding exists to support early-stage technologies with federal relevance, and Vis Viva Space's participation suggests some alignment with U.S. aerospace or mission-design priorities [sbir.gov]. More broadly, the company's open-source and commercial positioning could matter if customers increasingly prefer auditable, extensible engineering tooling over closed systems, but that remains a forward-looking inference from the business model label rather than a verified market outcome in public sources.
The main substitute markets are legacy engineering software suites, internal toolchains, and general engineering data-management workflows, although none are named directly in the available sources. That absence limits competitive precision, but it also clarifies the diligence question: whether customers view MBSE and design-data management as a separate budget line or as functionality expected inside existing engineering environments. If the latter, adoption may depend less on category creation and more on interoperability with incumbent systems, a point the public record does not yet resolve.
No independent source found -- This section relies primarily on company and SBIR award descriptions for market definition, with limited third-party corroboration and no named third-party market sizing study in the source set.
The Competitive Field
MIXED Vis Viva Space is positioning itself less as a full-stack aerospace CAD incumbent and more as an infrastructure layer for model-based systems engineering, with an open-source angle that could matter if engineering teams want a shared design-data repository rather than another closed workstation tool [sbir.gov] [visviva.space].
The evidence base here is thin, so the competitive map has to start with categories rather than a long list of verified peers. On the incumbent side, the company is clearly entering territory already shaped by established engineering-software vendors in MBSE, PLM, and simulation workflows, because its own SBIR description centers on integrating and automating analysis models for aerospace design through a continuous-integration pipeline [sbir.gov]. That framing implies competition for workflow ownership, not only for a single point tool. The adjacent substitute is the internal toolchain many aerospace programs already assemble from scripts, repositories, and commercial engineering software, which can be harder to displace than a direct software rival because it is embedded in team process rather than purchased as one product [sbir.gov].
The clearest edge visible from public material is product philosophy, not scale. According to the SBIR award description, Vis Viva Space is developing an open-source MBSE tool and design-data repository for aerospace engineering, and that can be a meaningful wedge in a market where interoperability, auditability, and engineering customization often matter as much as surface-level feature breadth [sbir.gov]. The same source says the system applies data-oriented programming architectures and continuous integration to aerospace design, which suggests an effort to treat engineering models more like versioned software assets [sbir.gov]. If that architecture works in practice, the durability would come from workflow adoption and repository gravity. If it does not, the edge is perishable, because the company appears to have only two employees and one confirmed federal award, which limits room for parallel product development, field support, and enterprise sales at this stage [sbir.gov] [sweetspot.so, 2026].
The biggest exposure is not a single named startup rival from the source set, because none is confirmed, but the structural advantage held by incumbent engineering platforms and by customer-built internal stacks. Incumbents typically benefit from installed bases, certification familiarity, procurement history, and broader module coverage, while internal toolchains benefit from being already accepted inside mission and design teams. Vis Viva Space has a 2025 first-award year and one confirmed federal award totaling $166,582, according to Sweetspot, so the public record still shows a company proving technical relevance rather than commercial distribution depth [sbir.gov] [sweetspot.so, 2026]. That matters because open source can widen top-of-funnel interest, but it does not by itself solve validation burden inside aerospace programs.
The most plausible 18-month scenario is a narrow but credible foothold in federally adjacent aerospace engineering teams if the SBIR-funded product becomes useful enough to slot into existing model and mission-design workflows [sbir.gov]. Winner if X: Vis Viva Space, if open-source adoption converts into repeat technical usage and a repository standard for a small set of design teams. Loser if Y: incumbent-independent internal tooling efforts, if teams decide maintaining bespoke pipelines costs more than adopting a purpose-built MBSE repository. The reverse case is also straightforward: established engineering vendors remain the practical winners if buyers continue to favor integrated suites and vendor support over a new open-source layer, especially while Vis Viva Space remains very small by headcount [sbir.gov] [prospeo.io].
No independent source found -- Competitive categories are inferred from the company's public product description, and the source set provides no confirmed named competitors or independent market-share evidence.
Opportunity
PUBLIC
The size of the prize is meaningful if Vis Viva Space can turn a narrow aerospace software tool into the system of record for how mission and design teams structure, share, and iterate engineering data across programs [sbir.gov] [visviva.space].
The headline opportunity is not a general engineering suite on day one. It is a credible shot at becoming default workflow infrastructure for a hard-to-serve corner of aerospace design, where model-based systems engineering, mission planning, and design-data management remain fragmented across tools and handoffs, according to the company's SBIR materials and website [sbir.gov] [visviva.space]. That outcome is still early and heavily company-described, but the path is at least legible: the company is already building around open-source MBSE, a design-data repository, and continuous-integration style automation for analysis models, which suggests a product aimed at recurring workflow rather than one-off consulting [sbir.gov]. The presence of a federal SBIR award and a first award year of 2025 also indicates that an external technical buyer found the problem statement credible enough to fund development, even if that does not yet establish commercial adoption [sbir.gov] [sweetspot.so, 2026].
| Scenario | What happens | Catalyst | Why it's plausible |
|---|---|---|---|
| Aerospace system of record | The product becomes the shared repository and workflow layer for mission design and MBSE teams at government-adjacent aerospace programs | A funded prototype converts into repeat use around a specific program workflow, with the SBIR-funded work serving as technical validation [sbir.gov] [sweetspot.so, 2026] | The company is explicitly building an open-source MBSE tool and design-data repository for aerospace engineering, which fits a system-of-record ambition more than a point utility [sbir.gov] |
| Open-core adoption wedge | The open-source layer attracts engineering users first, and a commercial layer forms around integration, governance, or mission-design workflows | Public release and user contribution around the open-source core, followed by paid workflow features [sbir.gov] [visviva.space] | The company describes both an open-source MBSE tool and mission-planning software, which is a common architecture for adoption-first enterprise software if execution holds [sbir.gov] [visviva.space] |
| Broader engineering platform | Aerospace becomes the proving ground, then the architecture extends into adjacent engineering domains that also depend on model integration and traceable design data | A successful aerospace deployment demonstrates that the data-oriented and continuous-integration approach generalizes beyond one vertical [sbir.gov] | The SBIR award description says the initial market is aerospace engineering software, with possible broader engineering applications, so adjacency is stated in the source, even if still aspirational [sbir.gov] |
What makes these scenarios interesting is the compounding logic if the first wedge works. A repository that sits in the middle of mission planning, systems models, and engineering analysis can become more valuable as more models, interfaces, and design decisions accumulate in one place, because each added workflow raises the switching cost for the next team and improves the usefulness of the underlying data structure [sbir.gov] [visviva.space]. In plain terms, one successful deployment could create a repeatable template: land with a technical team, absorb more analysis and mission-design steps into the same environment, then make the repository harder to replace because historical design context now lives inside it [sbir.gov].
The flywheel is still mostly prospective, and that should be stated plainly. Still, the early ingredients are visible in public materials: the product claim combines open-source distribution, a data repository, and automation of analysis models through a continuous-integration pipeline, which is the sort of architecture that can benefit from reuse, contribution, and deeper workflow embedding if adopted by engineers rather than imposed from management [sbir.gov]. With only a very small team publicly indicated, the near-term upside depends less on broad sales reach and more on whether one funded technical use case can produce a reusable product surface [sbir.gov] [prospeo.io].
The size of the win is hard to quantify from public evidence because no third-party market report or named public comparable appears in the supplied source set. The more defensible public framing is conditional: if Vis Viva Space were to become core workflow infrastructure for aerospace MBSE and mission-design teams, the company could support venture-scale outcomes because engineering system-of-record software tends to be sticky, deeply embedded, and capable of expansion across programs and adjacent design functions (scenario, not a forecast) [sbir.gov] [visviva.space]. At this stage, the upside rests on category position rather than demonstrated scale, but the category position itself is substantial if the company can move from funded R&D into recurring operational use.
No independent source found -- This section relies materially on company-described product scope from sbir.gov and the company website, with limited independent corroboration beyond the existence of a 2025 federal award and basic company-size signals [sbir.gov] [sweetspot.so, 2026] [prospeo.io].
Sources
Publicly reported
[sweetspot.so, 2026] VIS VIVA SPACE LLC (E8PEZAW6U267) | https://www.sweetspot.so/markets/federal/contractors/vis-viva-space-llc-e8PEZAW6U267/
[prospeo.io] Vis Viva Space company profile | https://www.prospeo.io/company-search/vis-viva-space
[rocketreach.co] Vis Viva Space Information | https://rocketreach.co/vis-viva-space-profile_b76e2672c53dae5b
Articles about Vis Viva Space LLC
- A Two-Person Startup Is Rewiring Aerospace Engineering's Spreadsheet Problem — The pre-seed startup is using a NASA SBIR grant to build a data-oriented programming tool for satellite and spacecraft design.