Skip to content

Business Track — README

Audience: Leadership, sales, prospect's CTO/CEO, customer evaluation team. Goal: Decide whether Evospin is a fit for your business in under an hour of reading. Every claim links back to a source file or an engineering doc; no marketing fluff. Companion tracks: ../delivery/ (PM/integration partners) · ../engineering/ (developers, SRE) · ../handover/ (onboarding + incident).

Quick references: Glossary — terminology · FAQ — common questions · Service catalog — operator inventory · Portal audit — verification report · Inventory — every doc in the portal.

Reading order

If you only have 30 minutes, read these in order:

  1. value-proposition.md — what Evospin is, why it exists, where it's actually differentiated.
  2. key-features.md — what's in the box, mapped to code paths.
  3. integration-options.md — how a customer plugs Evospin into their estate.

For commercial / contractual readers, continue with:

  1. nfr-sla.md — non-functional requirements, latency / uptime / RTO targets.
  2. roadmap.md — phased adoption plan, week-by-week.
  3. responsibilities.md — RACI for everything in the roadmap.

Pages in this track

# Page Read time Summary
1 value-proposition.md ~7 min Elevator pitch, differentiators (5-app monorepo, OTel-native, e2e tracing), build-vs-buy time-to-market argument, total LoC counted from find … wc -l.
2 key-features.md ~10 min Inventory of every shippable capability — auth, house games, provider games, live games, sportsbook, wallet, KYC, promo, real-time, admin — each with the owning module path and a doc-status marker (✓ / 🆗 / ⚠).
3 integration-options.md ~6 min What a customer can plug in or replace: white-label deploy, payment provider swap (CCPayment ↔ NowPayments ↔ SkinDeck), game provider adapter (Softswiss / PM8 / BGaming / EvoGames / ST8), KYC (Sumsub), captcha (GeeTest / reCAPTCHA), social auth. Per option: maturity, integration cost, owning file.
4 nfr-sla.md ~7 min Latency p95 targets per endpoint class, availability target, throughput ceiling, WS concurrency, RTO/RPO, security posture, compliance scope. Cross-references ../performance-testing.md.
5 roadmap.md ~5 min Phase 0 (Discovery) → Phase 5 (Launch) — deliverables, risks, who's accountable per phase.
6 responsibilities.md ~4 min RACI matrix: customer vs ebit-team for every roadmap deliverable. No "shared" rows — one accountable owner per line.
7 infrastructure-cost.md ~10 min Monthly OpEx in 4 scaling scenarios (Local / MVP / Growth / Scale). AWS eu-north-1 line-by-line + every paid SaaS dependency with sourced public pricing (2026-04 fetch) + variable per-event costs + top-5 optimization plays.
8 admin-platform.md ~6 min Guided, screenshot-led tour of the operator console grouped by product area (analytics, players, finance, catalogue, promos, affiliates, compliance, support, access control). Every screen captured live; backs onto the 57-view coverage catalog.

Total read time ≈ 56 minutes for the full track.

What you'll know after reading

  • [ ] Whether Evospin covers your iGaming use-case (casino + sportsbook + wallet + KYC + admin).
  • [ ] Which integrations you'd swap and how much work each is (S/M/L).
  • [ ] What latency and availability you can commit to your customers based on measured numbers, not aspirational ones.
  • [ ] How long it takes to go from contract signature to pilot.
  • [ ] Who owns what during onboarding.

What you won't find here

  • Commercial pricing for Evospin itself — handled in proposal, not in code. Infrastructure-side OpEx for an Evospin deployment is in infrastructure-cost.md.
  • Source code or implementation detail — see ../engineering/.
  • Live demo URLs — see your account team.
  • Regulator-specific certification status — see your jurisdiction lead. Evospin ships the integration surface (Sumsub for KYC, audit logs, provably-fair seeds); licensing is the operator's responsibility (nfr-sla.md §Compliance).