PARSIMON

Which Parsimon Is For Me?

Parsimon is the same runtime platform described in different languages for different buyers.

Canonical source: docs/public/overview/which-parsimon-is-for-me.md

Which Parsimon Is For Me?

Parsimon is the same runtime platform described in different languages for different buyers.

If a reader starts in the wrong section, the product can sound narrower or more abstract than it really is. This page gets people to the right narrative fast.

If you want the shortest overall product summary before choosing an audience, start with parsimon-in-90-seconds.md.

Start from the question you are trying to answer

If your question sounds like this You should start here Why
How do we integrate quickly without locking ourselves into one provider decision forever ../developers/product-overview.md This explains Parsimon as a developer-facing runtime with explicit control and optional automation
How do we move routing, context logic, and policy out of application code ../architecture/product-overview.md This explains Parsimon as a shared runtime boundary and platform decision layer
How do we control AI spend and make runtime choices more explainable to the business ../business_owner/product-overview.md This explains Parsimon as a governance and optimization layer for finance and executive stakeholders

The three canonical Parsimon modes

No matter which audience starts reading, the product should collapse back to the same three operating modes.

Canonical mode Short meaning
Transparent Control The caller chooses provider and model
Provider-Constrained Optimization The caller chooses the provider and Parsimon chooses the model
Full Runtime Optimization Parsimon chooses provider and model

Developer angle

Start here when the main concern is adoption friction, API compatibility, routing control, or context handling.

You will see Parsimon described as:

  • Transparent Control
  • Provider-Constrained Optimization
  • Full Runtime Optimization

Go to: ../developers/product-overview.md

Architect angle

Start here when the main concern is system shape, boundary placement, policy centralization, or how much logic should remain in application code.

You will see Parsimon described as:

  • Transparent Control
  • Provider-Constrained Optimization
  • Full Runtime Optimization

The architecture narrative also treats context handling as a separate boundary decision layered on top of those three modes.

Go to: ../architecture/product-overview.md

Business Owner and executive angle

Start here when the main concern is spend control, visibility, commitments, and which parts of optimization are handled centrally instead of ad hoc by engineering teams.

You will see Parsimon described as:

  • Transparent Control
  • Provider-Constrained Optimization
  • Full Runtime Optimization

Go to: ../business_owner/product-overview.md

Short version

Parsimon can be understood in one sentence for each audience.

  • For developers: integrate once, keep control where needed, automate where useful.
  • For architects: centralize routing, context, and policy in one runtime boundary.
  • For Business Owners: govern and optimize AI spend before it becomes a reporting problem.

Read next