For engineering managers, platform teams, and developer enablement
A new engineer builds a working slice of your architecture on their laptop. Local validators check the running containers, so completion records a working result against your services and conventions.
A paid design partner program for one working slice
company repo
private roadmap file
engineer laptop
Torollo + Docker + validators
company view
progress + result only
lab containersstay local
validator executionstays local
progress and resultsreported
A roadmap describes what the engineer must build and what Torollo should observe when the work is correct. The lab can follow the names, boundaries, and rules your team uses.
Private catalogue
Roadmaps are files in an open JSON format. Your team can review changes, version them, and update instructions when the internal stack changes.
scenario: service-onboarding
initialState: containers + network
validators: declarative checks
Completion evidence
When a check fails, it reports what it expected and what it found. The engineer changes the architecture and tries again. A pass means the validator observed the required state.
Security boundary
Torollo, Docker, the lab containers, and the validators run on the engineer’s machine. The pilot does not place a shared Torollo instance on a company server.
Team specificity
The scenario can encode the architecture names, dependency order, network access, and service state that matter to one working slice of your stack.
Manager signal
The intended Teams architecture reports roadmap progress and validation outcomes. Container state and validator execution remain local.
The pilot should answer one specific enablement need. It does not need to reproduce your full production environment.
Possible pilot
Ask a new engineer to assemble one service with the database, cache, proxy, or queue it depends on. The checks confirm each required component and connection.
Possible pilot
Encode which services should communicate and which paths should be blocked. Validators can probe the result against the running containers.
Possible pilot
Turn a bounded runbook into a sequence of changes with observable checks after each step. The engineer practices the procedure on an isolated local system.
Possible pilot
Begin from a prepared broken state. The roadmap supplies the goal and the validator supplies evidence while the engineer investigates and repairs the system.
Design partner workflow
The paid pilot exists to test the workflow with a real team before Torollo turns it into a broader product.
The pilot starts with one bounded onboarding outcome. We identify the services, network rules, configuration, and observable end state a new engineer should understand.
decision: pilot scope
The lab becomes a reviewable file in Torollo’s open roadmap format. Instructions, hints, initial state, and validators can be kept with the rest of your internal engineering material.
artifact: private lab
Each participant runs Torollo and Docker locally. The lab starts an independent copy of the architecture and checks it on that machine. There is no shared Torollo server to expose or maintain.
runtime: local Docker
Over the pilot, we learn where authorship is expensive, where engineers stall, and whether the completion signal is useful to managers. Those results determine whether a broader Teams product should exist.
output: pilot decision
The engineer completes a task on a live local system. The company receives the progress and result, not the container state.
What the pilot must prove
The first lab should represent a real part of your architecture without requiring the entire production estate.
The pilot tests Docker compatibility, machine requirements, and the setup path on the laptops engineers already use.
Managers and senior engineers review whether a pass represents the outcome the onboarding material is meant to teach.
Roadmap files are reviewable data. The pilot reveals the product support and authorship process needed after the first lab.
Paid design partner pilot
$3,000 to $5,000
6 to 8 weeks · one working slice
This is a design partner program. There is no self-serve Teams product yet. We turn one slice of your stack into a private onboarding lab, run it with your engineers, and use the observed results to decide what the product and pricing should become.
Describe the onboarding problemTell us who is onboarding, which part of the stack they need to understand, and what a working result would prove. We will use that to assess whether the pilot fits.
Talk to us at othmane@torollo.app