WORKFLOW INTELLIGENCE · EVIDENCE FIRST
Open a workflow, explore a repository analysis, or try a guided example. Watch Solve work — right now, in your browser.
Illustrative Studio workflow model. The actual workspace saves locally first and performs no external action by default.
Open StudioThe previews above describe real public tools. Open one to interact with the actual product.
01 / THE BOUNDARY
Solve shows you what it actually did — and what it did not do.
The browser preview runs a pinned WebAssembly build of SolveLang's canonical safe core with host side effects denied. It runs supported language behavior and returns deterministic output within that boundary without pretending it has unrestricted access to your machine, infrastructure, or production systems.
Inspect the browser-safe previewRepository-tested ≠ deployed
Deployed ≠ verified live
A sandbox ≠ unrestricted production execution
02 / THREE THINGS SOLVE DOES DIFFERENTLY
Give agents the right context
Solve Context prepares focused repository context for coding agents instead of treating an entire codebase as one giant prompt. Plan, pack, retrieve, and hand off the evidence that matters across supported agent workflows.
Inspect selected files and relationships, changed-path context, relevant graph evidence, and structured handoffs.
Explore Solve ContextUnderstand a system before changing it
Repository Audit and Solve Graph expose relationships across code, dependencies, validations, architecture, and security-relevant surfaces. Ask what depends on a file, which validations a change could affect, or where a workflow crosses a security boundary. Trace the evidence instead of relying on a confident guess.
Explore a sample auditModel workflows before automating them
Workflow Intelligence Studio gives you a structured place to model how work moves, where decisions happen, what can fail, and where a human needs to stay in control. Build the workflow. Inspect the risks. Run scenarios. Trace the outcome.
Studio is local-first by default. Projects stay in the browser unless you explicitly connect account saving.
Open Studio03 / THE FLAGSHIP
See the operation before you automate it.
Most automation tools begin with execution. Studio begins with understanding. Map the people, systems, policies, decisions, and failure paths that make up a real process. Then test scenarios against that model before turning the workflow into something production has to depend on.
Product-derived view of Studio's actual Projects, Canvas, Inspector, Scenario, and Trace surfaces. Open Studio to use the real workspace.
Build a visual workflow from canonical nodes and relationships. Capture actions, decisions, systems, owners, policies, SLAs, and human-review points.
Run deterministic analysis. Surface missing controls, risky paths, unresolved decisions, policy gaps, and failure paths.
Create scenarios and follow the modeled path. See branches, policy checks, pauses, and unresolved outcomes.
Projects save locally first. Optional account saving keeps a private copy across devices without replacing the browser-first workflow.
04 / SOLVE CONTEXT
Most agent workflows solve context the same way: dump everything into the window and hope the model finds what matters. That's noise with a token limit. Solve Context treats context as something you plan, not something you pile on.
Identify the files, relationships, and history that matter for this change.
Keep selected evidence structured, compact, and traceable to source.
Bring in relevant material as the task evolves, with exact provenance.
Pass a structured pack so the next agent inherits evidence.
What you get isn't a bigger context window. It's a smaller, traceable one — one you can follow back to source.
Real provider token and performance comparisons will be published only when the independent #898 evaluation supports them.
05 / WHAT WE VERIFY
Solve separates what is implemented from what is actually proven.
Deterministic behavior, traceable source evidence, explicit execution boundaries, and safety before side effects shape the product. Repository checks, browser acceptance, deployment verification, and live canaries are recorded separately.
Core analysis and validation paths have deterministic tests. Findings, relationships, context selections, and handoffs retain source provenance. Repository-tested does not mean deployed.
The public site, production customer-account infrastructure, and Studio account saving are deployed. Production API subscription billing, checkout, Stripe price validation, webhook signature enforcement, and billing-failure monitoring were verified enabled on September 17, 2026. The first real-payment canary is still pending, so broader public payment availability is not yet claimed. Paid priority and general managed execution remain separate gates.
Studio passed six authenticated acceptance checks and a bounded production save/reload, isolation, and local-first smoke. The temporary acceptance-origin cleanup remains a separate follow-up.
Current public status
Checking public surfaces…
Solve Context provider-token, latency, and quality comparisons will be published only when the independent #898 evaluation supports them.
BUILT WITH SOLVE
This space grows with real workflows, integrations, and projects built with Solve. Nothing here is fabricated.
06 / START WITH SOLVE
Model a workflow visually, inspect risks, run scenarios, and preserve the evidence. Projects save locally first.
Open StudioUse the published MCP server with supported agent workflows. Point it at the workspace to inspect using SOLVELANG_WORKSPACE_ROOT.
npx --yes @solvelang/mcp-serverValidate and run a repository example with the canonical native runtime.
git clone https://github.com/saiidz/solvelang.git
cd solvelang/solvec
cargo run -- validate ../examples/support_triage.solve
cargo run -- run ../examples/support_triage.solvecargo build --release
./target/release/solvec run ../examples/hello.solveRun the pinned WebAssembly safe core in your browser. Host access and side effects remain denied; the native CLI supports the full language.
Try SolveYOUR NEXT MOVE