Press I to close · arrows to move · A jumps to appendix
Steyble is an aggregation, routing and infrastructure layer. This round builds the product into a proper, diligence-ready asset — not a sales machine.
Steyble is an all-in-one financial aggregation platform. It connects decentralized and traditional financial services through one interface and one infrastructure layer.
A person who wants to buy, move, exchange, earn and spend digital assets today jumps across wallets, exchanges, bridges, staking sites, fiat providers and investment apps.
Six products. Six journeys. The user is the integrator.
One place to request the outcome. Steyble routes to the right provider.
Steyble does not need to manufacture every product. Licensed or specialized providers can perform the underlying service. Steyble provides the interface, routing and infrastructure.
The problem. A user would otherwise open several exchanges or DEX apps, compare prices, and execute the trade themselves.
Example. The user holds USDC and wants ETH. Steyble requests a route, shows the expected output after the platform fee, and the user signs once.
Benefit. One interface. Route aggregation. Same wallet context as the rest of the platform.
Monetization. Transaction fee on the swap — Back Office configurable; existing materials use a 0.3% default. B2B: fee share with the partner.
A blockchain network is like a separate rail. USDC on Ethereum is not automatically USDC on Solana. A bridge is the transfer between those rails.
Steyble is not a bank. The regulated payment activity is performed by third-party on-ramp / off-ramp providers. Steyble aggregates quotes and returns the user to the provider checkout.
Monetization. Spread / partner markup configured per tenant. Funds settle to the user’s destination address — Steyble keys are not on the value path. Live rails today include Changelly Fiat (and Trustodi for selected bank methods).
Yield is not guaranteed. Rates move. Principal can fall. Steyble shows available provider options; the user chooses and signs.
Each API needs development, monitoring, docs, keys and vendor management.
Primary message: integrate Steyble once instead of separately integrating every underlying service. One key, one envelope, à la carte services. v1 is a frozen contract.
Production Global API at api.steyble.com. At least one production partner is live (primarily prediction markets + wallet). Do not treat this as a disclosed volume figure — [DATA REQUIRED] for partner count, volume and revenue.
This is a structural thesis, not a claimed current flywheel metric.
| Stream | Status | Typical rate* |
|---|---|---|
| Swap / bridge / stake fee | Intended · live plumbing | 0.3% |
| Prediction markup | Intended · live plumbing | 0.3% |
| Perpetuals builder fee | Intended · live plumbing | 0.05% |
| Fiat spread / partner markup | Intended · live plumbing | Tenant-set |
| Card spend fee | Planned | Prior deck: 1% |
| Stream | Status | Model* |
|---|---|---|
| Revenue share on partner volume | Intended | ~30% platform / 70% tenant† |
| API / platform usage | Intended | Volume-based |
| White-label / enterprise | Planned / future | [DECISION] |
| Subscription / seat | Future | [DECISION] |
*Rates are Back Office configurable (`platform_fee_rules`), not hardcoded promises. †Prior investor deck split; perps/cards used a higher platform share in that table. Current revenue: [DATA REQUIRED].
A new service is a new provider adapter + fee rule + surface. The customer layer stays one app and one API.
These are structural advantages to build — not proven lock-in metrics today.
| Swap / DEX | Bridge | Wallet | Fiat ramp | Stake | Perps | Predict | B2B API | |
|---|---|---|---|---|---|---|---|---|
| 1inch / DEX apps | ● | ○ | ○ | ○ | ○ | ○ | ○ | ○ |
| LiFi / bridge tools | ○ | ● | ○ | ○ | ○ | ○ | ○ | ● |
| MetaMask / Rainbow / Zerion | ● | ○ | ● | ○ | ○ | ○ | ○ | ○ |
| MoonPay / ramp specialists | ○ | ○ | ○ | ● | ○ | ○ | ○ | ● |
| Lido / Aave front-ends | ○ | ○ | ○ | ○ | ● | ○ | ○ | ○ |
| Hyperliquid / venues | ○ | ○ | ○ | ○ | ○ | ● | ○ | ○ |
| Polymarket | ○ | ○ | ○ | ○ | ○ | ○ | ● | ○ |
| Steyble | ● | ● | ● | ● | ● | ● | ● | ● |
● = category Steyble already routes or exposes. Specialists remain deeper in their niche. Steyble’s claim is breadth + one integration — not “we beat 1inch at being 1inch.” Prior 16/16 scorecard is not restated as a fact.
Monthly gates in the appendix. This plan is the product-moat path — not a sales-acceleration plan.
12-month runway. Capital concentrates on product, routing, integrations and security — so Steyble is a proper company a buyer can acquire, not a sales experiment.
72% of the round is engineering + integrations + infrastructure/security. 8% is sales and marketing.
Equity %, valuation and instrument: [TO BE CONFIRMED]
| Category | Amount | % |
|---|---|---|
| Product & engineering | $630,000 | 42% |
| Provider integrations / liquidity | $270,000 | 18% |
| Infrastructure, security & monitoring | $180,000 | 12% |
| Legal & compliance | $150,000 | 10% |
| Sales & marketing | $120,000 | 8% |
| Operations / customer success | $90,000 | 6% |
| Contingency | $60,000 | 4% |
| Total | $1,500,000 | 100% |
Monthly figures in $000s. Sum = $1.50M. Cumulative used after M6 ≈ $660k · remaining ≈ $840k.
The destination is a strategic exit. This round is not a plan to become a large independent sales company.
If a later financing round is cleaner than a sale in 2027, that remains available. The organisation we build still points at exit, not at becoming a sales company.
| Weight | Metric | Today | 12-month target |
|---|---|---|---|
| Primary | Core flow success rate · latency · uptime | [DATA] | [TARGET] |
| Primary | Integrated providers / failover coverage | Live set on ecosystem slide | [TARGET] |
| Primary | API a partner can run without staff-on-call | /v1 live | Diligence-ready docs |
| Secondary | Design-partner usage · API volume | 1+ live partner | [TARGET] |
| Secondary | B2C active users · volume | [DATA] | [TARGET] |
| Watch | Revenue · burn · runway | [DATA] | 12-month plan held |
Prior-deck M12 ($618K ARR / 15k users) is not the scoreboard for this strategy. We will not spend the round chasing those numbers.
$1.5M from 10 September 2026. Product, routing, integrations, security. A diligence-ready aggregation company — not a sales team.
steyble.com · api.steyble.com
| Window | Product | Integration | Commercial | Ops / security | Gate | |
|---|---|---|---|---|---|---|
| M1 | 10 Sep–9 Oct | Stabilize core flows | Provider health dashboards | Pipeline hygiene | Monitoring + Sentry coverage | Baseline success rates |
| M2 | 10 Oct–9 Nov | API sandbox / docs | Fiat reliability | Design-partner list | Runbooks | Uptime baseline |
| M3 | 10 Nov–9 Dec | B2C UX pass on core | Failover design | Existing partner health | Infra hardening | Phase 1: operable without heroics |
| M4 | 10 Dec–9 Jan | API depth / docs | Additional swap or bridge provider* | Design-partner usage | Runbook complete | A second provider or deeper API |
| M5 | 10 Jan–9 Feb | Routing improvements | On/off-ramp reliability | Keep 1+ partner live | Incident drill | Routing measurable |
| M6 | 10 Feb–9 Mar | Status tracking hardening | Provider SLA draft | No sales blitz | Access review | Phase 2: layer is deeper |
| M7 | 10 Mar–9 Apr | Automation | Additional perps or quote source* | Inbound only | Capacity plan | Coverage up vs M6 |
| M8 | 10 Apr–9 May | Unit-economics instrumentation | Provider SLAs | Design-partner review | Backup / restore rehearsal | Gross margin visible |
| M9 | 10 May–9 Jun | Approved-roadmap only | Failover live if quality holds | No paid-acq spike | Security review | Phase 3: coverage + failover |
| M10 | 10 Jun–9 Jul | Reliability polish | Provider coverage +1 if quality holds | Usage evidence only | Automation | Ops transferable |
| M11 | 10 Jul–9 Aug | Docs / freeze new scope | Vendor cost review | — | Data room | Diligence pack |
| M12 | 10 Aug–9 Sep | Freeze · polish | No new unapproved services | Year review | Exit / next-step decision | Asset vs this deck |
*Only providers already on the approved investor roadmap (more swap / bridge / perps venues, failover). Cards only if KYB clears — not a committed monthly deliverable.
Illustrative internal split for this product-moat plan. Not vendor quotes.
| Category | Sub-allocations | Sum |
|---|---|---|
| Engineering $630k | Backend/API/routing $320k · frontend/mobile $120k · product/design $80k · QA $60k · tooling $50k | $630k |
| Integrations $270k | Provider work $130k · partner/liquidity $70k · vendor/API $40k · integration support $30k | $270k |
| Infra/security $180k | Cloud $55k · monitor/log $30k · security tools $30k · audit/pentest $40k · backup/secrets $25k | $180k |
| Legal $150k | Counsel/corporate $70k · regulatory $45k · contracts/privacy $25k · vendors $10k | $150k |
| Sales & marketing $120k | Existing-partner BD $50k · content/site $40k · tools $20k · events $10k | $120k |
| Ops $90k | Lean CS $40k · finance/admin $30k · tools $20k | $90k |
| M1 | M2 | M3 | M4 | M5 | M6 | M7 | M8 | M9 | M10 | M11 | M12 | Σ | |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Burn $k | 85 | 95 | 105 | 115 | 125 | 135 | 140 | 140 | 145 | 145 | 135 | 135 | 1500 |
| Cumulative | 85 | 180 | 285 | 400 | 525 | 660 | 800 | 940 | 1085 | 1230 | 1365 | 1500 | — |
| Remaining | 1415 | 1320 | 1215 | 1100 | 975 | 840 | 700 | 560 | 415 | 270 | 135 | 0 | — |
Figures in $000s.
| Capability | This plan | Why |
|---|---|---|
| Engineering (API, routing, app) | Highest | This is the asset |
| Product / design | High | Transferable UX |
| Security / DevOps | High | A buyer diligences this first |
| B2B sales / partnerships | Low | Support existing partners only |
| Growth / marketing | Low | Not a GTM round |
| Customer success | Low–medium | Keep live usage healthy |
| Compliance / ops | Shared | Company must stay clean |
Named future titles and FTE: [DATA REQUIRED]. Current roster: [DATA REQUIRED].
Internal sources: existing deck.steyble.com, docs/services/*, docs/partner/GLOBAL_API_INTEGRATION.md, docs/partner/COMPLIANCE_POSTURE.md, docs/known-limitations.md, brand book. Placeholders remain until the company fills them.