Veltic Managed

Build the whole backendin one project

Veltic is a managed platform for PostgreSQL, Node.js applications and background workers. Start with a database, add applications, functions, storage and realtime channels — administered from one dashboard.

Start your project Read the documentation

PostgreSQL

Managed PostgreSQL with a SQL editor, table editor, row level security and verifiable backups.

Stock Postgres, no dialect
Direct connections stay open
Backups you can download

Applications

Deploy Next.js, NestJS and Node into rootless containers with an HTTP probe and automatic rollback.

Functions

Background workers that outlive a request, for queues, syncs and scheduled jobs.

Storage

Store and serve files through short-lived signed tickets that never expose your API key.

Realtime

Broadcast, presence and live logs over project-scoped WebSocket channels.

Data API

Parameterized SQL over HTTPS for serverless runtimes that cannot hold a socket.

API Keys

Scoped keys and project boundaries so automation gets exactly the access it needs and nothing more.

Use one or all. Separate building blocks. Operated as one platform.

Stay productive and operate your stack
without leaving the dashboard

acme-productioneu-centralhealthy

-- connections by role

select usename, count(*) as connections

from pg_stat_activity

group by usename order by connections desc;

3 rows6 ms

usename	connections
velticControl	18
velticApp	9
ordersOwner	4

Query any database in the project

Run statements against any database, keep a history per database, and grant read and write as separate permissions.

Statement history
Read and write scopes
No local client required

Use Veltic with Next.js

None of this is a Veltic-specific client library. It is the driver, the framework and the fetch call you already use, pointed at a database and a runtime we operate.

import { Pool } from 'pg';

const pool = new Pool({
  connectionString: process.env.DATABASE_URL,
  max: 5,
  ssl: { rejectUnauthorized: true }
});

export async function getProducts() {
  const { rows } = await pool.query(
    'select id, name, price from products order by name'
  );
  return rows;
}

Read docs for Next.js

Kickstart your next project
with patterns that already work here

Browse the documentation

Next.js on Veltic

Standalone output, a pooled Postgres client and a deployment that rolls back when the HTTP probe fails.

A job queue without a broker

One table, FOR UPDATE SKIP LOCKED and a persistent worker. No Redis, no SQS, no extra bill.

Multi-tenant with RLS

Tenant isolation enforced by PostgreSQL rather than by remembering a WHERE clause.

Signed file uploads

Browser uploads straight to storage through a single-use ticket.

Live status with realtime

Broadcast events to connected clients over a project-scoped channel.

Serverless reads via Data API

Parameterized SQL over HTTPS from an edge runtime that cannot keep a socket.

Frequently asked questions

What is Veltic Managed?

A monthly plan for PostgreSQL, applications, functions, storage and realtime in the Veltic dashboard. After payment and activation you receive your account and a first project.

What does unlimited fair use mean?

The plan has no advertised per-feature quotas. Available server capacity, hard container limits and technical platform boundaries still apply. Unusual usage is reviewed internally.

Can I keep using my existing tools?

Yes. PostgreSQL remains PostgreSQL. Use direct connections, the HTTPS Data API or the CLI as appropriate. Next.js, NestJS and custom Node.js applications are supported.

Does Veltic provide end-user authentication?

No. Veltic authenticates platform accounts and API keys. Authentication for your application's own end users is something you implement, typically with row level security backing it in the database.

What happens if a payment fails?

You can still sign in and open billing. Platform mutations are blocked while a subscription is inactive and are restored after successful reactivation.

Is my data isolated from other customers?

Resources are scoped to a project, workloads run in rootless containers with dropped capabilities, and database roles are per database. Container isolation is not a dedicated virtual machine, and we will not describe it as one.