Branchly Cloud — PostgreSQL and database for web applications (2026)

TL;DR

Branchly Cloud (branchly.cloud) is DevStudio.it's serverless PostgreSQL platform — with Git-like branching (up to five parallel branches), an operations console (CRM, billing, helpdesk, automations), and EU data residency. In DevStudio projects the standard is Prisma + PostgreSQL: migrations in CI, DATABASE_URL in Next.js runtime. Branchly complements DevStudioIT Cloud (application hosting) — on devstudioit.com, the InfrastructureSplit section shows both products as the real layer split. Trial: 1 project, 0.5 GB and 20 CU-h/month. With deployment and the care package you get backups, monitoring, and post-launch support.

Who this is for

• Businesses and software houses building Next.js web apps that need a relational database with predictable costs and hands-on support
• Owners of business sites after a DevStudio.it launch — who want to know where data lives (forms, users, content) and who is accountable
• Developers looking for dev/staging environments without manually cloning production — a Branchly branch instead of "a second database on a VPS"
• Teams using Prisma who want migrations, connection strings, and backups in one ecosystem with hosting
• People comparing generic cloud databases with a solution aligned to the DevStudio stack — limits, EU residency, one point of contact

Keyword (SEO)

branchly cloud, database web application, postgresql nextjs, prisma migrations production, serverless postgresql eu, database branch dev staging, database_url nextjs, branchly devstudioit cloud, postgresql backup monitoring

What Branchly Cloud is — and what it is not

Branchly is the data layer in DevStudio.it — not app hosting. At branchly.cloud you get serverless PostgreSQL with usage-based scaling. One console combines:

EU data residency supports GDPR and B2B contracts. Branchly does not replace DevStudioIT Cloud — Cloud runs Next.js, Branchly holds persistence. Both appear in InfrastructureSplit on the DevStudio homepage.

When PostgreSQL — and when something else

The database choice on day one decides migration cost a year later. For most business web apps and B2B SaaS we build at DevStudio, the answer is consistent: PostgreSQL.

PostgreSQL makes sense when:

• You have relations — a user has orders, an order has line items, a company has many contacts
• You need ACID transactions — payments, bookings, inventory; a partial write is a bug, not a feature
• You run complex queries and reports — aggregations, JOINs, time windows; SQL in PostgreSQL is mature over decades
• You want JSON alongside relations — jsonb for flexible fields without giving up schema
• Your stack is Next.js + Prisma — generator, migrations, and TypeScript types are standard in our repos

When to consider other approaches

MySQL fits WordPress; for custom Node + Prisma, PostgreSQL wins. MongoDB with relations and reports usually ends in a SQL migration — costlier than starting on Branchly PostgreSQL.

Git-like branching — dev, staging, and preview

Branchly offers Git-inspired branching: up to five parallel branches per project — main, staging, feature branches, and PR previews without manual pg_dump.

Workflow: migrate on feature-x → test → merge to main → prisma migrate deploy on production; staging gets migrations earlier. In CI/CD with GitHub Actions, a branch per PR suits larger teams; smaller projects keep staging + main.

Prisma + PostgreSQL — standard in DevStudio projects

In client repos Prisma sits between TypeScript and PostgreSQL: schema.prisma defines models, prisma migrate versions schema, prisma generate supplies types for Server Actions and route handlers.

Typical layout:

// schema.prisma fragment — illustration
datasource db {
  provider = "postgresql"
  url      = env("DATABASE_URL")
}

model Lead {
  id        String   @id @default(cuid())
  email     String
  message   String
  createdAt DateTime @default(now())
}

Migrations in CI — not on a developer laptop "when convenient":

Branchly provides a connection string per branch. At DevStudio we do not commit URLs with passwords — DATABASE_URL lives in GitHub Secrets (build/migrate) and in the DevStudioIT Cloud panel (app runtime). Password rotation = change in Branchly + update env in Cloud + optional redeploy — no secrets in git log.

Connecting Next.js — DATABASE_URL and Server Actions

Next.js 15 with the App Router runs logic on the server: Server Actions, route handlers, cached fetch. All of it connects to the database through one variable DATABASE_URL — standard PostgreSQL, compatible with Prisma Client.

Configuration chain:

1. In Branchly create a project and branch (main for production).
2. Copy the connection string from the console.
3. In DevStudioIT Cloud paste it as env DATABASE_URL for the Next.js project.
4. In GitHub Secrets the same URL (or a separate one for migrations) for prisma migrate deploy in the pipeline.

Example Server Action with Prisma (simplified):

'use server';

import { prisma } from '@/lib/prisma';

export async function submitContact(formData: FormData) {
  await prisma.lead.create({
    data: {
      email: String(formData.get('email')),
      message: String(formData.get('message')),
    },
  });
}

With serverless PostgreSQL we configure Prisma with a limited connection pool — details at launch in care scope. NEXT_PUBLIC_* is frontend; DATABASE_URL is never public.

Operations console — CRM, billing, helpdesk

Branchly combines technical and operational layers: CRM (client context), billing (CU-h, storage), helpdesk (one support channel), automations (notifications without VPS cron). With DevStudioIT Cloud that is one ecosystem instead of five disconnected tools.

Backups, monitoring, and EU residency

A database without backups is a disaster license. Projects with the care package include procedures for:

• PostgreSQL backups in Branchly — schedule and retention per contract
• Monitoring of availability and metrics — alert before the client calls
• Restore testing — a backup nobody has restored is just a download link
• EU residency — operational data in European jurisdiction

Cloud monitors runtime, Branchly monitors PostgreSQL — care connects both layers.

Branchly + DevStudioIT Cloud — full production stack

Architecture shown in InfrastructureSplit on devstudioit.com:

Typical deployment chain:

1. Next.js repo with Prisma → Branchly project (main + staging).
2. Staging DATABASE_URL in staging project env in Cloud; production likewise.
3. Pipeline: PR builds and tests; merge to main → migrate + deploy on Cloud.
4. Handover: access to both panels, branch documentation, restore procedure in care.

Cloud + Branchly in the DevStudio ecosystem means one team and contract; hosting elsewhere + Branchly is possible, but env integration stays on you.

Branchly vs generic cloud databases

The comparison shows why Branchly is the DevStudio standard — not a ranking of external vendors.

Do not build client production on a random free tier and migrate later for GDPR and SLA — Branchly is a deliberate choice for this stack.

Trial plan and limits

Trial: 1 project, 0.5 GB, 20 CU-h/month — enough for a form PoC, staging + feature branch, and Prisma tests. Before go-live we align the plan to traffic and backups; serverless = pay for usage, hence monitoring in care.

Checklist before connecting production

• Production branch (main) separate from staging — different DATABASE_URL
• Prisma migrations in CI — migrate deploy on merge, not manually from a laptop
• DATABASE_URL only in Secrets and Cloud panel — nothing in the repo
• prisma generate in build step — types match production
• Form / write test on staging with staging domain, not localhost
• Backup and restore procedure agreed in care
• DB password rotation — clear who updates Branchly and Cloud
• Residency and data processing agreement — confirmed for end client

FAQ

Does Branchly replace DevStudioIT Cloud?

No. Cloud hosts Next.js; Branchly provides PostgreSQL. Use both with DATABASE_URL from Branchly in Cloud env.

How many branches in parallel?

Up to five — production, staging, dev, and feature previews. Remove temporary branches after merge.

Branchly without Prisma?

Yes — plain PostgreSQL. DevStudio standard is Prisma for migrations and Server Actions.

Trial limits exceeded?

Move to a production plan before client go-live — we align it with Cloud hosting and care.

EU data residency?

Yes — operational data stays in the EU, important for GDPR and B2B contracts.

Night-time DB outage?

With care, monitoring covers DB and app. Without care, response is on you.

Summary

Branchly Cloud is DevStudio.it's serverless PostgreSQL with Git-like branching, CRM/billing/helpdesk console, and EU data — the persistence layer aligned to Next.js, Prisma, and DevStudioIT Cloud. Instead of random managed Postgres you get dev/staging environments, CI migrations, DATABASE_URL in the hosting panel, and post-launch support. Trial (1 project, 0.5 GB, 20 CU-h/month) lets you validate the stack before production. If you are building a web app and asking "which database to choose" — in the DevStudio ecosystem the answer is: PostgreSQL on Branchly, with application delivery on Cloud.

Want a database for your Next.js project?

• Open Branchly Cloud — PostgreSQL, branches, and operations console
• Contact us — we'll match Branchly, DevStudioIT Cloud, and your Prisma pipeline
• Care package — backups, monitoring, and post-launch support