Connect your stack
27 native integrations. 3,200+ tools via managed connectors. Most are one-click OAuth, some use API keys - Viktor handles auth and starts working. No webhooks, no Zapier zaps.
Loading
Viktor is an AI employee that connects to Neon through a managed connector and helps you query and maintain application databases, running 35 Neon actions for you like Fetch, Search, and Run sql. Ask in plain English in Slack or Microsoft Teams; Viktor does the work in Neon and reports back. Setup takes about two minutes.
Free to start · No credit card · SOC 2 Type 1 · Works in Slack & Microsoft Teams
Messages you'd actually send. Paste one into Slack or Microsoft Teams, swap in your specifics, and Viktor takes it from there.
“Query Neon for last month's signups and summarize the trend.”
— you, in Slack or Teams
“Check Neon for slow queries this week and flag the worst offenders.”
— you, in Slack or Teams
“Sync new records from Neon into a sheet every morning.”
— you, in Slack or Teams
“Watch Neon for a spike in errors and alert me with the likely cause.”
— you, in Slack or Teams
Ask in plain English in Slack or Microsoft Teams. Viktor picks the right Neon actions, runs the work, and reports back. No workflows to build.
Search across all organizations, projects, and branches by keyword. Returns matching items with id, title, and URL. Query must be at least 3 characters. Do not use when you need all projects (use listprojects instead).
List all organizations the current user belongs to. Supports optional search parameter to filter by name or ID.
Get details and configuration of a specific Neon project. Do not use when you need to list all projects (use listprojects instead).
Get a PostgreSQL connection string for a Neon database. All parameters are optional; the tool resolves the project, branch, and database automatically if not specified. In read-only mode, this tool can only return connection strings for read-replica endpoints. If no read replica exists and the user needs a DATABASEURL, explain that limitation and guide them to to copy the DATABASEURL manually.
List all tables in a Neon database. Do not use when you need column-level detail for a specific table (use describetableschema instead).
Fetch detailed information about a specific organization, project, or branch using the ID returned by the search tool.
List compute endpoints for a project or branch. Do not use when you need a connection string (use getconnectionstring instead).
List the log fields (labels) you can filter on for a branch, such as servicename, severitytext, scopename, and entitytype. Use this before querylogs or listlogfieldvalues to discover valid field names.
Reset a branch to its parent's current state, discarding all changes made on the branch. NEVER run autonomously; always ask the user first. Use preserveUnderName to preserve the current state under a new branch name before resetting.
Delete a branch and all its data. NEVER run autonomously; always ask the user first. For deleting an entire project, use deleteproject instead.
Complete a query tuning session by either applying the changes to the main branch or discarding them. NEVER run autonomously; always ask the user first and verify on the temporary branch.
Complete a database migration by applying changes to the main branch and cleaning up the temporary branch. NEVER run autonomously; always ask the user first and verify in the temporary branch.
Delete a Neon project and all its data. NEVER run autonomously; always ask the user first. For removing single branches, use deletebranch instead.
Create a new Neon project with a default database and branch. If someone is trying to create a database, use this tool. Returns a connection string for the new project automatically. Supports optional orgid (assign to a specific organization) and name parameters.
Analyze the query execution plan for a SQL statement using EXPLAIN ANALYZE. Do not use when you need to execute the query for results (use runsql instead).
Create a branch in a Neon project for isolated development or testing. By default the branch is created from the project's default branch; pass parentId to fork an existing non-default branch instead (e.g. to make a disposable copy of a dev/staging branch).
Get column definitions, data types, and constraints for a specific table. Do not use when you need all tables in a database (use getdatabasetables instead).
List projects shared with the current user for collaboration. Do not use for projects you own (use listprojects instead). Supports optional search (filter by name or ID) and limit (default 10) parameters.
List Neon projects in your account. Do not use for projects shared with you (use listsharedprojects instead). Supports optional search (filter by name or ID) and limit (default 10) parameters.
Get a tree view of all objects in a branch, including databases, schemas, tables, views, and functions. Do not use when you only need table names (use getdatabasetables instead) or column detail (use describetableschema instead).
List the distinct values of a log field (e.g. all servicename or severitytext values seen) within a branch and time window. Use this to discover concrete values to pass to querylogs. Only advertised fields (from listlogfields) resolve; others return an empty list.
27 native integrations. 3,200+ tools via managed connectors. Most are one-click OAuth, some use API keys - Viktor handles auth and starts working. No webhooks, no Zapier zaps.
Message Viktor in Slack like you'd message a teammate. "Query Neon for last month's signups and summarize the trend." "Check Neon for slow queries this week and flag the worst offenders." Plain English, any tool.
Viktor opens Neon, runs the work, and posts back what changed. Sensitive actions wait for your approval. Everything is logged. You stop doing the work and start reviewing it.
A Neon AI agent is an AI that connects to your Neon account and completes work in it - it doesn't just answer questions about Neon, it takes the actions. Viktor is that agent: an AI employee that works in Neon on your behalf and delivers the finished result in Slack or Microsoft Teams.
Unlike workflow builders such as Zapier or Make, there is nothing to configure - no triggers to map, no workflows to maintain. You describe the outcome in plain English, and Viktor picks the right Neon actions, chains them with the other 3,200+ tools it connects to, and asks for approval before anything sensitive runs.
The database developers trust, on a serverless platform designed to help you build reliable and scalable applications faster.
Managed connector authorization - Viktor never sees your password, and you can revoke access at any time.
Review-first approvals: sensitive Neon actions wait for your sign-off before they run.
Isolated compute per team, encrypted in transit and at rest - and your data is never used to train models.
SOC 2 Type 1 compliant, with Type 2 and ISO 27001 in progress.
Yes. Neon is one of the 3,200+ tools Viktor connects to, via a managed connector. Once connected, anyone on your team can put Viktor to work in Neon from Slack or Microsoft Teams - no workflow builder, no code.
Ask for outcomes that span tools — Viktor pulls from Neon, cross-references the rest of your stack, and delivers one finished result.
Viktor connects to 3,200+ tools and works across them in a single run.
