Skip to content
RunningLake

Early access

Forty conversations, then a product.

We are looking for eight to twelve design partners, and two or three should be CDC-heavy — those are the ones who will tell us whether a whole phase of this plan should exist at all.

  • Twelve months at 70% off.
  • Direct Slack access to the engineers building it, not a support queue.
  • Roadmap influence, in writing, on the phases you actually depend on.
  • A written case study when there is something real to write about.

We charge from the start. Even $500 a month changes the quality of the conversation entirely — a free pilot produces polite feedback, and an invoice produces the truth.

Being straight about where we are: the product is pre-release. The control plane, the router’s constraint layer, the data-plane Terraform module and the platform bundle are built. The engines, the cost meter and the agents are in progress. If you need a platform in production this quarter, we are not it yet.

Email us first

founders@runninglake.com reaches the same two people. One of us usually answers the same day, and the answer comes from whoever wrote the thing you are asking about. It is also how you get into the console, for the reason below.

There is no form on this page. There was one, and it posted to an endpoint that did not exist — so every submission was lost, and nobody saw an error. A mailbox is less impressive and it works.

Three things make the reply useful instead of a round of questions:

  • Your company, and roughly how big the data team is.
  • What you run today — Databricks, Snowflake, a self-assembled stack, nothing yet.
  • The one thing you would want fixed first.

The console, once we have added you

The console is at swim.runninglake.com ↗ and sign-in works — for addresses on our list. The Google app behind it is still in testing, so anyone we have not added is refused at the account picker and never sent back, and we do not see the attempt. Email first and we will add you. After that the console creates the workspace itself. Google is the only provider configured, and the screen is headed “Sign in” because returning users land on the same one.

RUNNING

A workspace, and a ninety-day trial. No card. A personal email address earns a smaller trial than a work one, and the pricing page says by how much.

BUILDING

More than one engine, and enforcement of the storage cap. A query runs on DuckDB, in a sandbox, on a data plane that reports it can — Trino, Spark, StarRocks and Flink are not deployed to one yet, so the router has nothing to choose between. Your compute is measured per query and the period’s cap is enforced: cross it and the next query is refused, by name, before it is sent. Storage is measured about every fifteen minutes by a plane that reports it can — with no plane bound, nothing measures it at all — and it is not enforced: nothing refuses a write for being over.

This page has no form and nothing behind it to receive one. The request for it is logged like every other request to this site — Privacy says what that line holds.