Skip to content

An engineering practice for difficult system decisions.

Stratorys helps experienced technical teams select, design, and harden data-intensive systems when performance, scale, and reliability become architecture problems.

A deliberately narrow practice.

The consequential choices concern data shape, storage, access patterns, software boundaries, and operational behavior. Production AI systems have the same requirements for provenance, resumability, and testability.

Stratorys works where these decisions are expensive to reverse. Adjacent work such as reliability, telemetry, and implementation is part of the engagement when it supports that outcome.

Founder

Lucas Jahier.

Founder of Stratorys and a software and data engineer. Lucas works across software and data systems, with a focus on clear system boundaries and durable technical decisions.

What you can inspect.

Public software and writing show how we reason about system boundaries, transparent automation, and technical trade-offs.

Open source

Cueto

A knowledge-as-code implementation that keeps organizational facts in versioned files and validates them in CI.

Read the design study
Open source

Pratrol

A pull-request triage system with inspectable routing, prioritization, and rationale.

Read the design study
Technical writing

Query engine selection

A practical method for evaluating query engines through workload, operations, and durable trade-offs.

Read the guide

How an engagement runs.

01

Frame

Make the system, decision, and operating context explicit.

02

Evaluate

Test the relevant alternatives and record the trade-offs.

03

Deliver

Recommend or implement, with the reasoning and operational knowledge attached.

Discuss the system decision.

Share the system, the uncertainty, and what makes the next decision difficult to reverse.

Contact Stratorys