OEM — product integration

Your interface.
Our engine.

Three products, three brands, three design teams that never met. The figures below are computed right now, in your browser, by the same engine.

Three fictional brands — Boréal, Clarté, Volta.Under the skin: three specs, one engine.

Boréal Assuranceillustration_vie_entiere

Illustration — whole life · F age 353 variables · 30 steps · deterministic

Cash surrender value at 65valeur_rachat[30]—
Projected death benefitcapital_deces[30]—
Premiums paidprime × 30—
Powered by ASTRIA—
Clarté Hypothèqueamortissement_canadien

$450,000 loan · 25 yrs · 4.89%2 variables · 300 steps · deterministic

Monthly paymentpaiement—
Interest over 25 yearssomme(interet[t])—
Balance after 5 yearssolde[60]—
Powered by ASTRIA—
Volta Patrimoinedecaissement_stochastique

Drawdown · $1.25M · 30 years2 variables · 30 steps · 2,000 scenarios

Capital sufficient to age 951 − ruine—
Median wealth at year 30p50[30]—
Pessimistic scenario (P10)p10[30]—
Powered by ASTRIA—

The bottom strip never changes: brand, colors, and type belong to the client — the run fingerprint belongs to ASTRIA.No number moved. Only the skin fell away — exactly what your customers never see.

White-label — shared ownership

What stays yours. What we guarantee.

You keep the product, the customer relationship, and perceived value. We take the part nobody wants to maintain: the compute, its version, and its proof.

You

What your customers see

  • Brand, colors, typographyyour design system
  • Journeys and UIyour front end
  • Commercial assumptionsyour rates, your fees
  • Pricing and billingyour model
  • Customer relationship & supportyour team

ASTRIA

What nobody sees

  • Compute executiondeterministic
  • Spec versionsigned in the Registry
  • Run ID and fingerprintper execution
  • Replay of a past resultsame seed → same output
  • Audit trailspec · seed · run

Integration — one request

A spec goes in. A projection comes out.

Your app sends the declarative spec; ASTRIA returns the projection and run ID. No formulas copied into your code, no engine to maintain. Here is exactly the call behind the Clarté Hypothèque screen above.

  1. {
  2. "scenarios": 1,
  3. "steps": 300,
  4. "variables": [
  5. {
  6. "name": "interet",
  7. "formula": "solde[t-1] * 0.00402262"
  8. },
  9. {
  10. "name": "solde",
  11. "init": 450000,
  12. "formula": "solde[t-1] + interet - 2589.12"
  13. }
  14. ]
  15. }

Response — amortization

✓ sealed run
StepInterestPrincipalBalance

300 steps returned · payment — · fingerprint —

Audit — what your customers never see

Three products, one audit trail.

Each screen on this page produced a run. Replay them: duration varies by device, the fingerprint never. That is how you replay, three years later, the exact illustration a customer signed.

Run registry

Shared seed 0x88A0AD7F · three distinct specs

ProductSpecKey outputDurationFingerprintVerification

An identical fingerprint after replay means none of the thousands of computed values moved by a cent.

Put your brand on it.

Describe your product and the volume you expect. We will look together at what it does in your UI, with your assumptions.

Frequently asked questions

Let's discuss your use case

Describe your product and estimated volume. An email will open with this information.

Reply within 1 business day · No commitment

Or write to richard.beauregard@subspacecomputing.com · API documentation