Tabnine
Privacy/compliance-focused AI coding assistant and agents with strong on-prem/air-gappe…
Privacy/compliance-focused AI coding assistant and agents with strong on-prem/air-gapped deployment, selling into finance, defense, and pharma. One of the longest-standing, most enterprise-entrenched assistants (regulated-industry footprint); now ships agentic workflows. Self-hosted/IDE-plugin posture →
Roadmap
Status
OAuth + audit-log polling
Pattern
Managed SaaS — nothing to install
Runtime
Not yet published
SDK version
Readiness
What “Roadmap” means for Tabnine
On the integration roadmap. The platform-side spine for this framework's pattern is already shipped — what remains is the per-framework adapter. Selecting it in the dashboard opens the “Get notified” path rather than creating an actor.
How it attaches
OAuth + audit-log polling.
Authorise Trustvice once via OAuth; Trustvice then polls Tabnine's audit-log API on a recurring schedule. No code changes.
Authorise Trustvice via OAuth so Trustvice can pull the platform's audit log on a recurring schedule. No code changes required.
- 1
Initiate the OAuth flow
Click “Connect” next to Tabnine in Settings → Integrations. Trustvice generates a state token and PKCE challenge, then redirects you to the provider's authorize URL.
- 2
Authorise on the provider
Sign in to Tabnine with an account that has audit-log read permissions and approve the requested scopes.
- 3
Trustvice schedules the poller
The callback exchanges the code for access + refresh tokens, encrypts them at rest, and schedules the first poll cycle (default 60–120 seconds).
- 4
Verify
Within a couple of poll cycles, audit entries land in Witness. The Integrations page shows last-poll timestamp, records ingested, and any errors.
# Dashboard navigates here: GET /api/oauth/authorize/tabnine?workspace=ws_abc123 # Trustvice 302s to the provider's authorize URL with PKCE, # the provider redirects back to: GET /api/oauth/callback/tabnine # Trustvice exchanges code → tokens → schedules the audit-log poller
Tabnine is on the roadmap. The steps above describe how the integration works on the OAuth + audit-log polling pattern — whose platform-side spine is already shipped — but the Tabnine-specific adapter isn't generally available yet. Tell us you're running it and we move it up the queue.
Coverage
Coverage pending.
The captured-event list is published once the Tabnine adapter ships. Every adapter normalises into the same canonical Witness record, so the dashboard, queries, exports, and lens evaluations are identical regardless of which events a given runtime emits.
The full pattern guide
OAuth + audit-log polling — end to end.
Every framework on this pattern shares the same platform-side spine, endpoints, and gotchas. The pattern guide covers them in full.
Read the OAuth + audit-log polling guideNeed help landing Tabnine?
Talk to the integration team.
We help you land the integration end to end — including the parts that live in your environment.
Request integration help
Trustvice 360