Supabase plugin for Kimi Arrives Across Kimi Code and Kimi Web.

Supabase is extending its AI development footprint with a new integration for Kimi. The database platform has launched the Supabase plugin for Kimi across Kimi Code and Kimi Web, giving developers another way to combine an AI coding environment with a Postgres-based backend.

The company announced the plugin on LinkedIn, saying it is designed for building with Kimi K3 and Supabase. The announcement was brief, however, and did not detail the plugin’s permissions, supported operations, setup process, pricing, or plan requirements.

The confirmed scope is narrow but relevant. The plugin is available in both of Kimi’s main development surfaces:

• Kimi Code, the coding-focused environment
• Kimi Web, Kimi’s browser-based interface
• Kimi K3, the model referenced by Supabase for the combined workflow

That availability could let builders use Kimi while working on applications backed by Supabase, rather than treating the AI assistant and backend platform as disconnected tools. Supabase has not yet specified whether the plugin can inspect database schemas, generate queries, manage projects, or execute changes. Those capabilities should not be assumed from the announcement alone.

For small teams, the practical value will depend on how much verified project context the plugin can provide to Kimi. AI coding systems are more useful when they understand the real structure of an application, but deeper access also creates questions about permissions and change control. A plugin that only supplies documentation would be materially different from one able to query or modify a live project.

The launch also fits a broader pattern of Supabase connecting its backend platform to AI interfaces. Supabase later introduced a connector for Perplexity, allowing users to query Postgres data, look up users, and invoke Edge Functions from a chat, as Create With previously covered. Those capabilities are documented for the Perplexity connector, but Supabase has not said that the Kimi plugin offers the same access.

Before using the integration with a production application, developers should establish exactly what the plugin can see and do. The initial announcement leaves several operational questions unanswered:

• Whether access is read-only or includes database and project changes
• How authentication and project selection work
• Whether permissions can be limited by environment or role
• Whether Kimi retains project context, prompts, or returned data
• Which Supabase and Kimi plans support the integration
• Whether plugin actions produce logs or require confirmation

A sensible first test would use a non-production Supabase project containing synthetic data. Developers can then check whether Kimi correctly understands the schema, whether suggested code matches the project configuration, and whether any action requires explicit approval. Generated migrations and queries should still be reviewed before execution, particularly when they affect permissions or existing records.

The integration gives Kimi users a more direct route into the Supabase ecosystem, but its significance will ultimately depend on the technical documentation. For now, the concrete news is availability across Kimi Code and Kimi Web. The depth of the connection remains unclear.

What is Supabase plugin for Kimi?

Supabase plugin for Kimi is an integration intended to help developers build applications using Kimi K3 and Supabase together. Supabase says it is available through both Kimi Code and Kimi Web, but has not published a detailed list of supported actions.

Where is the Supabase plugin for Kimi available?

Supabase says the plugin is now available on Kimi Code and Kimi Web. The announcement does not describe geographic restrictions or a staged rollout.

Does the Supabase plugin for Kimi require a paid plan?

Supabase did not provide pricing or plan requirements in its announcement. Builders should check the plugin listing and their Supabase and Kimi account interfaces before configuring it for a project.