Veltic Managed
Build the whole backendin one project
Veltic is a managed platform for PostgreSQL, long-running applications and background workers. Deploy any of 13 runtimes into rootless containers, then add functions, storage and realtime channels — administered from one dashboard.
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 13 runtimes from Node and Python to Go, .NET and your own Dockerfile, 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.
The platform
Five building blocks, one machine
Database, auth, storage, compute and realtime are not five vendors stitched together. They are five services on the server you rent, addressed through one CLI and one dashboard.
A real PostgreSQL, not a subset of one
Every project gets its own database and its own role. Extensions, row level security, point in time backups and a connection string you can hand to psql.
- Isolated role per database
- Row level security from the dashboard
- pg_dump backups with restore
- iduuidnot null
- tenant_iduuidnot nulltenant boundary
- total_centsbigintnot null
- created_attimestamptznot null
policy "tenant reads its own orders" using (tenant_id = current_setting('veltic.tenant')::uuid)
create table orders (
id uuid primary key default gen_random_uuid(),
tenant_id uuid not null,
total_cents bigint not null check (total_cents >= 0),
created_at timestamptz not null default now()
);
alter table orders enable row level security;
create policy "tenant reads its own orders"
on orders for select
using (tenant_id = current_setting('veltic.tenant')::uuid);Stay productive and operate your stack
without leaving the dashboard
| 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;
}13 runtimes,
one container contract
Listen on the port you are given and answer an HTTP request. Beyond that, the language is yours — and the one that is missing arrives as a Dockerfile.
Ship the build
- NestJSApps
- Next.jsApps
- Node.jsApps and functions
Upload the finished output. Nothing is compiled on the server, so the container starts immediately.
Install at start
- PythonApps and functions
Dependencies are resolved when the container starts. The first start takes longer, later ones do not.
Compiled for you
- GoApps and functions
- ASP.NET CoreApps and functions
- RustApps and functions
- JavaApps and functions
- BunApps and functions
- DenoApps and functions
- PHPApps
- RubyApps
Built before the start in a throwaway container with capabilities dropped. Dependency caches survive deployments.
Bring a Dockerfile
- DockerApps and functions
Any language at all, including the ones not listed here. Same isolation, your own base image.
Kickstart your next project
with patterns that already work here
Browse the documentationNext.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. Applications run in 13 runtimes — Node with Next.js or NestJS, Python, Go, ASP.NET Core, Rust, Java, Bun, Deno, PHP and Ruby — and anything else ships as a Dockerfile.
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.
Build the whole backend in one project
One plan, one dashboard, one command line interface. PostgreSQL, applications, functions, storage and realtime.