`Vercel CLI` Adds Experimental Native Binaries Without Node.js

// related

• #0001

  #0001Infra & SaaSSimon Willison13 hours ago

  `Datasette` `1.0a31` adds write SQL and stored queries

  60radar

  DatasetteSQLite data tool — publishes DBs as web UI and APIs

  Permissions now cover insert/update/delete workflows directly in the SQL UI. Good fit for lightweight internal admin tools on SQLite, but still alpha.

  • —Users with the right permissions can run write queries against a database, turning Datasette from read-only browsing into a small data editing surface.
  • —Stored queries replace the old canned-query naming and can be saved privately or shared with other members of the same instance.
  • —The new execute-query UI starts from templated insert, update, and delete queries for editable tables, reducing hand-written SQL mistakes.
  • —Permission checks block operations like create table when the user lacks that grant, so this can back simple ops panels without opening full DB access.

  Source: simonwillison.net/2026/May/29/datasette/#atom-everythingRead original →
• #0002

  #0002Infra & SaaSGeekNews16 hours ago

  `Garnix` Hosting Shuts Down on July 15, 2026

  50radar

  GarnixNix-based hosting SaaS — open-source self-hosting path

  The hosting service is ending during the Shopify transition. Users get an open-source escape hatch, but hosted workloads need migration planning now.

  • —Garnix hosting ends on July 15, 2026; any production or preview workloads must move before that date.
  • —The codebase is being open-sourced, so self-hosted or shared community instances can replace the managed service.
  • —Community instance operation is still only partially described, so treat it as a migration path, not a guaranteed managed alternative.

  Source: news.hada.io/topic?id=29974Read original →
• #0003

  #0003Infra & SaaSvercel_blog16 hours ago

  `Vercel Sandboxes` Adds Public Binding for Port `8080`

  40radar

  Vercel SandboxesCloud sandbox runtime — runs code on Vercel infrastructure

  Apps can now bind 8080 directly through the ingress domain. Small but useful when templates, dev servers, or agents assume 8080 by default.

  • —Port 8080 was previously reserved for the sandbox controller; that controller moved to 23456, freeing the common app port.
  • —Ingress support means services listening on 8080 can be opened directly, reducing custom port rewrites in sandboxed dev flows.
  • —This mostly helps compatibility with existing templates and tools. Not a platform shift, but fewer sharp edges in Vercel previews.

  Source: vercel.com/changelog/port-8080-is-now-available-in-verceRead original →