Vix.cpp
Open-source C++ developer platform
Vix.cpp provides developer tooling and foundations for building modern C++ systems. It is maintained by Softadastra and represents an important part of our existing open-source work.
explore Vix.cppCompany
A computing research and technology company working toward infrastructure-independent computing.
We research and build systems that progressively separate software from the infrastructure executing it.
01
Can software be separated from the infrastructure that executes it?
Modern applications are deeply coupled to infrastructure. Developers choose machines, regions, databases, replication strategies, accelerators, recovery systems, deployment topology and cloud services long before an application begins executing.
Softadastra is exploring a different computing model: applications express their requirements while the computing system determines how available infrastructure can satisfy them.
This is the long-term problem around which the company is being built.
02
Softadastra combines existing open-source engineering with longer-term runtime and computing systems research.
Open-source C++ developer platform
Vix.cpp provides developer tooling and foundations for building modern C++ systems. It is maintained by Softadastra and represents an important part of our existing open-source work.
explore Vix.cppIntent-driven adaptive runtime
The Runtime is the core execution technology behind our infrastructure-independent computing direction. It is being developed to progressively move infrastructure decisions out of application code and into the computing system.
explore Softadastra RuntimeReference computing hardware
A future low-power reference machine designed to run the Softadastra Runtime and participate in a computing fabric without becoming a hardware dependency for applications.
explore Softadastra Node03
Vix.cpp ↗ is Softadastra's open-source C++ developer platform.
Our long-term research does not begin from a presentation or a hardware concept. We already spend time building and maintaining developer infrastructure.
Vix.cpp gives us a practical environment for working on C++ tooling, build systems, developer experience, runtime integration and future programming models.
It also keeps Softadastra connected to a simple requirement: research must eventually become software developers can actually use.
04
Intent + State + Constraints → Softadastra Runtime → Computing Fabric
The Softadastra Runtime ↗ is currently in development.
It is the execution layer where our research is intended to become executable technology.
Over time, it is intended to take increasing responsibility for placement, scheduling, distributed state, replication, recovery, reconciliation, trust, resource selection and adaptation.
These are engineering and research targets. Runtime capabilities are being implemented and validated progressively.
05
Applications should describe what they need to accomplish, the state they require and the constraints that must be respected.
Placement, scheduling, resources, recovery and infrastructure selection should increasingly become responsibilities of the computing system.
Applications should not have to be permanently redesigned because execution moves between local machines, edge systems, cloud infrastructure or future hardware.
Where application requirements permit it, loss of Internet connectivity should not automatically mean loss of computation, state or usefulness.
Infrastructure-independent computing should not require expensive proprietary machines. Efficiency and hardware diversity are part of the research problem.
06
Infrastructure-independent computing crosses multiple areas of computer science and systems engineering. We do not expect a single abstraction to solve it.
07
The machine should be replaceable. The application should remain.
Softadastra Node is our planned reference hardware direction: a small, efficient computing resource designed around the Softadastra Runtime.
It is deliberately not the foundation of the architecture. Softadastra software should also be able to use existing local machines, edge infrastructure, cloud resources and future hardware.
The purpose of reference hardware is to demonstrate what the Runtime can do on a known, low-cost environment, not to create a new infrastructure dependency.
08
Turn research questions into small working systems instead of keeping the architecture theoretical.
Test behavior, performance, resource consumption, recovery and failure modes.
Remove assumptions that fail and refine the programming and execution models.
Move progressively from individual runtime capabilities toward a larger computing fabric.
09
Some of the best way to understand Softadastra is to read the code.
Vix.cpp is open source and the Softadastra Runtime is being developed publicly on GitHub.
That gives developers, researchers and potential collaborators a way to evaluate the technical direction from actual work rather than only company descriptions.
10
Softadastra is being built around a technical thesis rather than a single temporary product category.
The immediate work is concrete: maintain developer technology, build the Runtime, validate individual capabilities and test them on real hardware.
The larger opportunity is a computing layer capable of spanning machines and infrastructure without forcing applications to encode every infrastructure decision themselves.
If successful, that direction can become useful across developer infrastructure, edge systems, unreliable networks, local computing, cloud environments and new classes of hardware.
11
We are interested in people and organizations who care about difficult computing systems problems.
Explore the repositories, challenge the architecture, contribute code and work with us on the systems problems behind the Runtime.
explore the open source ↗If you are interested in long-term computing infrastructure, developer technology, edge computing or adaptive runtime systems, we are open to conversations about the direction.
softadastra@gmail.com ↗Software expresses intent. Infrastructure satisfies it.