Company profile · 3 min read
Arbital: a social terminal for stocks, crypto and perps
Arbital combines market discovery, stocks, tokenized equities, perpetuals and automated market-making strategies in one non-custodial trading interface.
Published · Updated
What it does
Arbital is a trading terminal for memecoins, stocks, tokenized equities and perpetuals, with automated market-making and grid strategies across multiple venues. The current homepage presents one balance, trending-market discovery, 640+ global stocks and ETFs, perps with up to 40x leverage, and maker strategies across 14+ perp DEXs. The docs say the platform is non-custodial and that funds remain in the user’s wallet.
The fit is an experienced crypto or cross-market trader who understands leverage, liquidity and smart-contract risk. Arbital is not a beginner investment app despite its social/mobile ambition. The product compresses discovery and execution into one surface, which makes the risk controls and custody boundary more important than the convenience pitch.
Why I’d look closer
The product has a distinct social-trading angle: trade ideas, trending assets and top-trader calls sit alongside execution. The company reports that 2,700 traders moved $1.35B in volume in its first seven months and that monthly volume reached about $435M. Those are company-reported trading metrics, not proof of profitability, liquidity quality or user outcomes.
The founder context is unusually relevant. The YC profile describes Karon Pangestu as an early Aevo growth/product leader, Steven Mulyawan as a former Aevo partnerships lead, and Vincent Owen Toniwan as an exchange and market-making infrastructure engineer. The profile claims sub-2ms latency at 100K events/second in prior systems; that is background/company-reported context, not a promise for every Arbital venue.
What I’d ask
Which entities operate each market, how are tokenized stocks issued and monitored, and what happens when a DEX, oracle, bridge or wallet connection fails? I’d inspect liquidation, max-loss, withdrawal, fee and jurisdiction controls before considering any trade. The public sources checked did not expose a simple consumer price card.
My editorial take
Arbital is interesting as a unified execution and discovery layer for sophisticated traders. The docs and non-custodial claim make the product inspectable. The correct editorial posture is “understand the rails first,” not “trade because the volume is large.”
Quick facts
| Field | Sourced detail |
|---|---|
| Buyer fit | Experienced crypto, perp and cross-market traders |
| Product surface | Stocks, tokenized equities, memecoins, perps and market-making strategies |
| Public risk signals | Up to 40x leverage; non-custodial claim; verify venue and liquidation details |
| Traction signal | Company reports 2,700 traders and $1.35B volume; not performance proof |
Sources checked
Checked 2026-09-19.
| Source | Used for |
|---|---|
| YC company profile | Product, founders and company-reported volume |
| Arbital homepage | Current markets, leverage and strategy surface |
| Arbital docs | Non-custodial and strategy documentation |
Cohort context
Arbital is listed in Summer 2026. In our 2026-09-18 directory snapshot, 16 of 232 listed companies in that cohort have YC’s primary industry label Fintech (6.9%). This is a current-directory comparison, not an original intake count or a performance ranking. Nine-cohort dataset.
Public website snapshot
Observed 2026-09-19T16:18:34.788Z in raw homepage HTML. This records visible metadata and advertised links, not agent execution or product quality.
| Signal | Homepage observation |
|---|---|
| Product description metadata | Observed |
| Canonical link | Not observed in this response |
| H1 or H2 heading | Observed |
| Typed structured data | Not observed in this response |
| Docs/developer link | Observed |
| Pricing link | Not observed in this response |
| llms.txt link | Not observed in this response |
| Markdown alternate | Not observed in this response |
Public observations · Collection method. Missing links here do not establish that a capability or file is absent elsewhere.
