Request and verify an email one-time code without sending the user through an embedded login page.
Wisent trading · native on macOS
Your trading assistant, in a focused Mac app.
Byk signs you in natively, securely retains the session in Keychain, and opens the Wisent trading assistant already authenticated inside a first-class macOS shell.
Availability: Byk is on commercial hold. There is no standalone checkout, paid entitlement, or independent public launch.
Trading assistantAuthenticated
01Native sign-inEmail one-time code
→02Session seedKeychain to web cookie
→03Trading surfaceRetained WKWebView
Page state remains visibleReload · Sign out
The authenticated Supabase session is persisted in Keychain and seeded into the trading surface.
Loading age, cookie readiness, and WebKit failures remain visible without replacing the retained page.
How it works
A native boundary around the existing trading product.
Byk does not implement trading or assistant logic. It owns native authentication, session persistence, the application shell, and hosting the existing web surface.
Authenticate and persist
Requests and verifies the sign-in code, then stores the resulting session under ai.wisent.byk.session.
Open already signed in
Seeds the Supabase SSR cookie at document start before loading the Wisent trading assistant.
Web boundary →Keep status actionable
Shows real load and session errors, page freshness, Reload, and Sign out around the retained trading page.
Product boundaries →Clear ownership
Byk hosts the surface. It does not become the surface.
- Owned hereNative sign-in, Keychain persistence, WKWebView session seeding, app shell, and signed updates.
- Owned elsewhereTrading logic, assistant behavior, and account management stay in the Wisent web product.
- Network boundarySupabase auth, the trading web surface, and an optional HTTPS Sparkle update feed.
Product documentation
One home for the client and trading reference.
Read the supported macOS client architecture and boundaries, plus the held trading platform's economy, runtime, API lifecycle, release provenance, and endpoint configuration.