Fetching from the wire…
01
02
03
04
05
06
07
08
Public story · 2026-07-30 · high
The hosting platform bills per vCPU-month and gives every app a forkable VM snapshot and shared SQLite database.
Why now: The listing was climbing Show HN at 62 points as of July 30, before any word on real agent usage beyond the launch thread itself.
Kedge launched a hosting platform that lists SSH, Git, and HTTP APIs for AI agents as a core audience, per its Show HN listing. For teams that adopt it, an agent over SSH can rack up charges past the $5 free tier with no one approving the spend. The rates: $15 per vCPU-month and $5 per GB-month for memory. Storage runs $0.05 per GB-month, egress $0.01 per GB.
It also covers static sites, serverless functions, full-stack apps, and databases, all globally distributed. Every app gets a shared filesystem and what Kedge calls a global SQLite database. The same data layer follows the app across regions instead of sitting in one place.
Forkable VM snapshots round out the pitch: a copy of a running app's full state can branch off the way a git repo does. That sits alongside SSH and Git access built specifically for agents, not just developers typing commands by hand.
One bet: the agent running the SSH session is the customer, not the developer who signed up for the account. Pricing per vCPU-month only pays off if agents keep running up usage after the demo ends. Nothing in the listing says how many of Kedge's current users are agents versus developers testing it by hand.
That listing was climbing Show HN at 62 points as of July 30, before any word on real agent usage beyond the launch thread itself.
Each link below shares sources, entities, or timing with this story.
OpenClaw uses SQLite / Shared entity: SQLite / Shared topic / Earlier coverage / Tension
Linked by a graph relationship (OpenClaw uses SQLite); both cover SQLite; overlapping topics (agent, database).
OpenClaw uses SQLite / Shared entity: SSH / Shared topic / Earlier coverage / Tension
Linked by a graph relationship (OpenClaw uses SQLite); both cover SSH; overlapping topics (agent, apps).
Lobsters uses SQLite / Shared entity: SQLite / Shared topic / Earlier coverage
Linked by a graph relationship (Lobsters uses SQLite); both cover SQLite; overlapping topics (apps, databas, sqlite).
mempalace uses SQLite / Shared entity: SQLite / Earlier coverage / Tension
Linked by a graph relationship (mempalace uses SQLite); both cover SQLite; earlier SQLite coverage from 2026-06-05.
DuckDB benchmarked against SQLite / Shared entity: SQLite / Earlier coverage / Tension
Linked by a graph relationship (DuckDB benchmarked against SQLite); both cover SQLite; earlier SQLite coverage from 2026-06-18.
Shared entity: SQLite / Shared topic / Earlier coverage
Both cover SQLite; overlapping topics (agent, apis, database, sqlite); earlier SQLite coverage from 2026-06-24.
OpenClaw uses SQLite / Shared entity: SQLite / Earlier coverage
Linked by a graph relationship (OpenClaw uses SQLite); both cover SQLite; earlier SQLite coverage from 2026-06-02.
OpenClaw uses SQLite / Shared entity: SSH / Earlier coverage
Linked by a graph relationship (OpenClaw uses SQLite); both cover SSH; earlier SSH coverage from 2026-03-16.