Work with MLambda
Four ways to engage, starting with seeing it run. Terms are agreed per engagement.
-
Demonstration
See Turing run on a domain you describe — from a paragraph of requirements to a checked model and generated source, live.
- You bring a business description; we take it through backlog, requirements, model and verification
- The refusals matter as much as the results — you will see what the model will not accept and why
- Generated source on the MLambda runtime, with its specifications and deployment beside it
- A written follow-up on what an engagement on your system would involve
Write with two or three sentences about the system and the invariant that worries you most.
-
Consulting
Architecture and delivery with the MLambda stack, for teams that need a system to be correct rather than merely shipped.
- Actor-model and reactive system design on MLambda.Actors
- Distributed data on MLambda.Data, or specification-first design of your own store
- Formal specification in Z and model checking in TLA+ for the parts that must not fail
- Language and compiler tooling on Genesis — domain languages, parsers, generators
Write with a description of the system and its hardest invariant.
-
Commercial licence and support
For the commercial-tier products — Turing, Data, Aleph, UI and OS — and for supported use of the open ones.
- A licence for the product and its updates
- A support channel with a named engineer
- Upgrade guidance across versions
- Priority on defects that affect your deployment
Write with the product, the deployment topology, and the timeline.
-
Early access
Access to private builds and repositories for teams evaluating the commercial tier before committing to it.
- Builds and source for the product under evaluation
- Direct contact with the engineer who built it
- A defined evaluation window and exit criteria
- The option to convert to a commercial licence
Write with the product you want to evaluate and what you intend to build with it.