Supabase + EVDSOFT

EVA by EVDSOFT provides an AI-assisted integration layer for Supabase projects. Authorized users can connect supported Supabase projects and surface project metadata, database structure, operational information and related technical context within EVA. EVA uses this information to help teams understand their infrastructure, identify operational signals and interact with supported workflows through permission-aware interfaces.

Beyond EVA, EVDSOFT's custom software projects can also run on Supabase-based backend infrastructure (Postgres database, authentication, storage) today.

This page documents the scope, data access, permission model and security approach of the EVA ↔ Supabase integration. The EVA-specific connection described below is currently in development; each capability is explicitly labeled as Available, In development or Planned.

General Supabase backend compatibility is available today. The EVA-specific connection includes:

• Connecting a Supabase project — in development
• Secure authentication — in development
• Project metadata — in development
• Database schema view — in development
• Operational logs — in development
• Usage information — in development
• AI-assisted technical analysis — in development
• Permission-aware actions — in development

How it works

In the planned architecture, EVA connects to an authorized user's Supabase project with a scoped, read-oriented connection; project metadata, schema structure and operational signals (logs, usage) become readable inside the EVA interface. The AI layer summarizes this information and surfaces technical insight; any action requiring a write or change goes through explicit user confirmation (permission-aware).

Connecting your Supabase project

Once released, authorized users will be able to connect a supported Supabase project directly from EVA; project selection and scope approval happen at connection time, under the user's control. This flow is currently in development.

Authentication & authorization

The connection is designed to be established through Supabase's own authorization mechanisms; EVDSOFT does not aim to store your Supabase account credentials in plain text within its own infrastructure. Full authorization-flow details will be published here before the integration goes live.

Permissions

The permission model is designed to be permission-aware: EVA only reads within the scope a user approves at connection time, and any action that would modify schema or data requires a separate confirmation step.

Data accessed

Data categories planned to be accessed by the integration:

• Project metadata (project name, region, plan-level information)
• Database schema (table/column structure - not row-level data)
• Operational logs (error/operation records)
• Usage information (usage/capacity indicators)

AI-assisted analysis

The technical signals above are designed to be summarized and interpreted by EVA's AI layer - the goal is helping teams understand their infrastructure faster and notice operational signals (e.g. rising errors, approaching capacity limits). AI analysis interprets existing data; it does not take autonomous action on your Supabase project.

Security

The Supabase integration is being built under EVDSOFT's general integration security principles: least-privilege access, role-based access, user confirmation for risky actions, and auditability. EVDSOFT does not expand permissions beyond what the provider grants.

Disconnecting the integration

The connection is designed to be removable by the user at any time from the EVA panel. Once disconnected, EVA's access to the related Supabase project ends.

Data retention

The general principle is that the integration retains only the data required for EVA's function. A definitive retention and deletion-request policy will be published here before the integration goes live.

Troubleshooting

As the integration is still in development, there is no published troubleshooting guide yet. Common scenarios will be added here once the connection is live.

Support

For questions about the Supabase integration, reach us at [email protected] or via our contact page.

Changelog

• September 16, 2026 — Supabase integration documentation published (general backend compatibility available, EVA-specific connection in development).