Models
Different reasoning and production models can be routed by job. Customers hire the role, not a model name.
Technology overview
Stromation separates probabilistic reasoning from deterministic controls. Models propose and produce work. Code enforces permissions, budgets, state, and the public boundary.
The combination creates a worker that can hold a job across sessions.
Different reasoning and production models can be routed by job. Customers hire the role, not a model name.
Approved capabilities provide controlled access to research, files, systems, measurement, and publishing workflows.
Business context, prior work, decisions, known limits, and performance history persist outside a single conversation.
Workers can wake on a bounded schedule or trigger instead of waiting for a person to start every interaction.
A directing role can assign narrow work to specialist workers and review what they return.
Sessions, actions, results, costs, failures, and published artifacts form an operating record.
Per-run limits and company ceilings stop work when the approved budget is exhausted.
Hosted runtime, database state, public-safe event publication, versioned code, and recovery procedures support operation.
Permissions, cost ceilings, allowed event types, public data boundaries, and quality checks are enforced in code and data rules where the current system supports them.
Stromation Live reads only two curated public tables and keeps private company state out of the browser.