Features
Four feature sections: a statement with a numbered index, a hairline grid, tabbed details and a by-the-numbers layout. 4 variants below.
(01) Statement and index
Halyard / Deploys
The release page your on-call engineer actually wants open at 2 a.m.
Halyard puts the merge queue, previews, rollbacks and the audit trail on one screen. Here is what each part does.
One queue per environment
Merges line up in the order they were approved. Halyard rebases each one on the last green build, so main never breaks on a race.
A preview for every branch
Each push gets its own URL with seeded data, torn down 48 hours after the branch merges or goes quiet.
Rollback is a single action
The previous build stays warm for 24 hours. Rolling back swaps traffic in under four seconds, no rebuild involved.
Every change is on the record
Who shipped what, when, and who approved it, exportable as CSV for the quarterly audit nobody enjoys.
* Timings measured on the Halyard Team plan, Frankfurt region, September 2026.
Install Dependencies
1npx shadcn@latest add https://ui.devsloka.in/r/feature-floating-showcase.json
(02) Feature grid
(Features)
Postgres, with the parts you used to script yourself.
Ferro runs standard Postgres and handles branching, backups, replicas and pooling around it. Six things you get on day one.
- 01
Branching databases
Fork production into an isolated copy in about two seconds. Schema and data, copy-on-write, so a 400 GB branch costs what it changes.
Up to 50 branches per project
- 02
Point-in-time restore
Pick any second from the last 30 days and restore to a new branch. Your current database keeps serving traffic while you look.
30-day window on Pro
- 03
Read replicas in four regions
Frankfurt, Virginia, Singapore and São Paulo. Replication lag sits under 80 ms at the 95th percentile.
p95 lag, Aug 2026
- 04
Query insights
The ten slowest statements of the day, with plans, call counts and the deploy that introduced them.
- 05
Connection pooling
A built-in pooler holds 10,000 client connections against 120 on the server. Serverless functions stop exhausting your limit.
Transaction mode
- 06
Plain Postgres 17
No forked engine, no proprietary SQL. pg_dump works, extensions work, and leaving takes one command.
62 extensions enabled
Install Dependencies
1npx shadcn@latest add https://ui.devsloka.in/r/features-block.json
(03) Tabbed features
Kestrel for support teams
Four things your queue does differently on Kestrel.
Pick one to see how it works. Numbers come from 212 teams that switched between January and June 2026.
01 / 04
Routing that reads the ticket
Kestrel looks at the customer's plan, the product area and the language, then routes to whoever resolved the closest match in the past 90 days. If that person is offline, it falls back to the team queue instead of guessing.
- Rules editor for the cases you want to pin by hand
- Round-robin fallback per team
- Every routing decision shows its reason
Install Dependencies
1npx shadcn@latest add https://ui.devsloka.in/r/feature-interactive-cards.json
(04) By the numbers
(By the numbers)
Fast enough that you stop noticing the deploy.
We publish these every quarter, including the ones that got worse. This is where Tern stands today.
- Median build
- 9s1
- Down from 41 seconds before the shared cache. Most rebuilds only touch the files that changed.
- Edge regions
- 14
- Deploys go out to every region at once. Rolling back takes the same single click.
- Uptime, last 12 months
- 99.98%2
- Two incidents, both under 20 minutes, both written up publicly the same week.
- Deploys a month
- 3.1M
- From weekend side projects to teams shipping forty times a day.
Install Dependencies
1npx shadcn@latest add https://ui.devsloka.in/r/features-block-four.json