Integration Model
Connect hosts, billing, runtime visibility, and project memory without collapsing them into one surface.
Orqint keeps the public site, hosted Workspace, and local companion aligned. Use supported hosts and operators tools without losing slices, project context, or local ownership.
GitHub
OpenAI
Anthropic
Slack
Stripe
Linear
Supabase
Vercel
Supported surfaces
Browse the tools and product surfaces around Orqint
Every integration has a clear role: customer account workflows in the hosted app, runtime control in the companion, and execution in the CLI or supported host bridges.
See supported hosts
Supabase
Session and customer state wire into the hosted app without pulling project truth into the cloud.
What the Orqint ecosystem is composed of
Marketing explains the model, the hosted app owns account state, and the local companion keeps runtime control close to the repo.
Hosted account layer
Auth, billing, subscriptions, and team membership live on app.orqint.com.
Local companion
Projects, repos, slices, contexts, and live operations stay visible from the local dashboard.
Host bridges
Use Cursor, Claude Code, Codex, and future adapters with the same governed runtime model.
Billing and compliance
Commercial state is explicit instead of leaking into the runtime surface.
Shared design system
Marketing, app, and companion all use the same token contract with surface-specific compositions.