Updated September 29, 2026. On September 23 Databricks released Genie App Builder and App Spaces in Beta, and the apps Genie App Builder builds scale to zero when idle. Nothing has shipped under the name serverless micro apps, and code-first apps still cannot scale to zero; that the Beta runtime is what the June post called micro apps is our reading, not something Databricks has said. We also updated horizontal scaling, now generally available on AWS, and the XLarge size, now in the docs.
Databricks serverless micro apps are the scale-to-zero runtime for Databricks Apps that Databricks announced at Data + AI Summit 2026 and set out in a blog post dated June 16, alongside App Spaces and Genie App Builder: each app runs in its own lightweight virtual machine, starts when needed and scales down to zero when idle. The post said all three were "coming to Databricks Apps, with private previews coming soon." On September 23, 2026, App Spaces and Genie App Builder reached Beta, and the release note says the apps Genie App Builder builds "scale to zero when idle." So scale to zero is out, in Beta, but only for apps built with Genie App Builder inside an App Space; a code-first app, one you write and deploy yourself, still runs on an instance size you pick and is billed while it runs. The name did not ship: as of September 29, 2026, micro apps appear on none of the 46 Databricks Apps docs pages, in no AWS platform release note from June through September, and nowhere on the Databricks Apps product or pricing pages. Calling the Beta runtime the June micro apps is our inference, not a Databricks statement.
Key facts
- Status: announced June 16, 2026 with "private previews coming soon." Since September 23, 2026, App Spaces and Genie App Builder have been in Beta behind a Previews toggle named Governed agentic app-building, and the apps built there scale to zero. No Databricks page gives serverless micro apps a status of its own. Our roadmap trackers for Serverless Micro Apps, App Spaces and Genie App Builder follow all three.
- Runtime, as announced: "a new micro VM-based runtime" in which each app can "start up fast when needed, scale all the way down when idle and stay isolated from other apps."
- Runtime, as shipped in Beta: apps built with Genie App Builder "run on an isolated, on-demand serverless runtime inside an App Space", zero to one instance, scaled down after a default 30 minutes idle, with "a short cold start" on the next request. The docs never say virtual machine.
- Price: "During Beta, there is no charge" for Genie App Builder, App Spaces or the apps it builds, and "Pricing for Beta features is subject to change." Code-first apps are still "billed per hour of compute time while running, based on provisioned capacity." So the June promise that a lightweight app "becomes usage-based, not reserved capacity-based" is still untested.
- Still not published: a price after Beta, a cold start time, CPU and memory for the on-demand runtime, whether the idle timeout can be changed, a scale-to-zero option for code-first apps, or a migration path for existing apps.
What Databricks said about serverless micro apps
The name comes from one blog post, "Enabling Governed Vibe Coding for Enterprise Apps on Databricks", dated June 16, 2026 and signed by Evan Pandya, Justin DeBrabant and Cong Xu; we keep it at our news permalink for the post, which links to the original. It names "three new key capabilities for Databricks Apps":
- App Spaces, "a new governance boundary to configure resources, access management, and security policies for groups of apps."
- Genie App Builder, "a purpose-built AI app authoring tool for Databricks with native awareness of your data assets, Unity Catalog semantics and workspace context." For the rest of the Genie family, see Genie One vs Genie Agents vs Genie Code Explained.
- Serverless micro apps: "A new class of Serverless Micro Apps that start up fast when needed and scale down to zero when idle, so organizations can support a broad portfolio of apps without the cost of always-on infrastructure."
Databricks' own sentence on how the three fit: "App Spaces establishes the governance layer before a single app gets built, Genie App Builder creates inside that layer, with full awareness of your data and workspace context, and microVM-based serverless micro apps make the whole model economically sustainable at scale." In the post, micro apps are the runtime underneath the other two, and the post says nothing more technical about them than the runtime lines quoted in the key facts above.
What shipped on September 23
The September 2026 AWS release notes carry an entry dated September 23, "Build governed data and AI apps without code (Beta)": Genie App Builder builds apps from natural-language prompts inside an App Space, "and the apps scale to zero when idle." The Genie App Builder docs page, last updated September 25, is the first docs page to describe that runtime in technical terms:
- Apps "run on an isolated, on-demand serverless runtime inside an App Space" and are built with Databricks AppKit, "the Databricks framework for data and AI apps."
- Each app "scales between zero and one instance" and scales down after "a default 30 minutes of idle time." The first request after that meets "a short cold start"; no figure is given.
- Memory and local disk are lost on scale-down. The docs say to keep state in a Lakebase table, a Unity Catalog volume or another external store.
- "If you need an always-on app or horizontal scaling, use a dedicated-instance app." We read that as the docs' name for an ordinary, instance-sized app; the term appears on no other Apps docs page.
- During Beta there is no charge for Genie App Builder, App Spaces or the apps, and pricing "is subject to change."
- Beta regions: 10 on AWS and 18 on Azure; "GCP, GovCloud regions, and Mooncake (Azure China) are not supported." Partner-powered AI features must be on at account and workspace level, apps have no general public internet egress, and packages come through a Databricks-managed npm and PyPI proxy.
To get it, a workspace admin turns on Governed agentic app-building from the Previews page and creates an App Space, which the App Spaces docs (last updated September 28) define as "a governance boundary where admins define who can create and use apps." Anyone with CAN CREATE APP permission on a space can then build from the Build tab on the Apps home page, and apps in a space run under a serverless usage policy.
None of those pages, nor the release note, says micro app, micro VM or virtual machine. The one Databricks page after June 16 that uses the micro VM idea is a transcript of the Data + AI Summit 2026 talk "Databricks Apps for Everyone" by Fabian Jakobs, posted September 15: the App Builder deploys, in the transcript's words, "two serverless microVMs" that "are like the scale to zero kind of apps." It is an automatic transcript, not documentation, and it never says micro apps.
So our reading, and it is only ours: the June post put a scale-to-zero runtime under App Spaces and Genie App Builder, and on September 23 those two shipped on one. We treat that runtime as the micro apps of June under the App Builder name. Databricks has not said so, and nothing published offers it outside Genie App Builder.
What it changes, and for which apps
For a code-first app, nothing has changed yet. It "runs as a containerized service on the Databricks serverless platform" and is "billed per hour of compute time while running, based on provisioned capacity." You choose an instance size when you create or edit the app; the AWS docs now list three and default to Medium.
| Size | CPU | Memory | Rate | Where it is listed |
|---|---|---|---|---|
| Medium (default) | Up to 2 vCPUs | 6 GB | 0.5 DBU per hour | Docs and pricing page |
| Large | Up to 4 vCPUs | 12 GB | 1 DBU per hour | Docs and pricing page |
| XLarge | Up to 12 vCPUs | 48 GB | 3 DBU per hour | Docs and pricing page |
The XLarge row reached the AWS docs after our September 16 check. The REST API accepts XLARGE, but the CLI reference still lists only LARGE and MEDIUM for --compute-size, and the Azure docs still show two sizes. The pricing page's worked example prices the DBU at $0.75 on the AWS Premium tier: "5 Medium apps for 30 days and 24 hours each day" is 1,800 DBUs and "a final charge of $1,350 for the entire month." Divide by five, our arithmetic not theirs, and in that example an always-on Medium app is $270 a month whether or not anyone opens it. There is no idle state for these apps: an app is "Running, Stopped, Deploying, or Crashed", Running is billed. The only instance-count fields in the REST API, compute_min_instances and compute_max_instances, belong to horizontal scaling, where the docs give the range as 1 to 5; nothing documents a floor of zero for a code-first app.
That is the model the post argues against. "Using always-on, dedicated compute means paying for capacity that is often not in use," it says. "The economics of traditional app infrastructure are less favorable for smaller, more specialized apps," meaning departmental tools and line-of-business workflows that are "used in bursts and idle most of the time." The promised change is one sentence: "The practical outcome is that deploying a lightweight app on Databricks becomes usage-based, not reserved capacity-based." So the $270 is the number a micro app is meant to cut. For apps built with Genie App Builder, the Beta answer is all of it, since they cost nothing during Beta. What they will cost after Beta, and in what unit, nobody has said, and the pricing page has no line for them.
What Databricks still has not published. A price or billing unit after Beta. A cold start time: the docs say "short" and give no number. CPU and memory for the on-demand runtime, or whether the 30-minute idle default can be changed. Whether a Streamlit, Dash, Gradio or Node.js app can run on it; the docs only say App Builder apps use AppKit. Any scale-to-zero option or migration story for code-first apps, or what the CLI's new --space flag, "Name of the space this app belongs to", means for how such an app runs. Anything that fills those gaps is a guess.
What code-first apps can do instead
Stopping the app yourself. A Stopped app "is not accessible and doesn't incur any costs. Databricks preserves the app's configuration and environment, so you can restart it without reconfiguring." The CLI has a stop command, databricks apps stop [NAME]; the app details page documents six tabs and does not document stopping. This is scale to zero by hand: free while off, unreachable while off, and someone has to restart it. In-memory state does not survive the restart, though anything written to a Lakebase database does: "Any schemas or tables created by an app remain even after you re-deploy or stop the app."
Horizontal scaling, which goes the other way. An app can run "across multiple instances behind a single app URL for higher availability and concurrency." A release note dated September 29, 2026 made it generally available on AWS; the Azure docs page still says Beta. You convert a standard app from its Settings tab, up to 5 instances per app and 20 such apps per workspace, and "Compute cost scales linearly with the number of instances." The AWS and Azure what's-coming pages both say it switches on for compliance-profile workspaces in early October 2026. It scales out, not down: the floor is still one running instance.
Lakebase, the platform's scale-to-zero precedent. The AWS and Azure what's-coming pages say "Lakebase Autoscaling adds autoscaling and scale-to-zero" and that "With elastic compute replacing fixed-size instances, most customers will see a reduction in compute costs." Same shape of claim, made for a database, and already rolling out. Neither page mentions scale to zero for Apps; that arrived through the September 23 release note, and only for apps built with Genie App Builder.
How to follow it
Our roadmap trackers for Serverless Micro Apps, App Spaces and Genie App Builder follow the three names, and all three are listed as sub-features on the parent Databricks Apps roadmap tracker, where a fourth sibling, Apps on Databricks Marketplace, has already moved to Public preview. Recent items mentioning Databricks Apps land hourly on the Databricks Apps topic hub. The trackers read public sources only; we do not see the private roadmap.
On September 16 we named three signals that would make micro apps real. Two have fired, in substance if not in name:
- A docs page with a preview notice. Since our September 16 check, two new Apps docs pages, Genie App Builder and App Spaces, have appeared with a Beta banner telling a workspace admin to turn on Governed agentic app-building from the Previews page. Neither page says micro app.
- A release-notes entry under Databricks Apps. The September 23 entry says the App Builder apps "scale to zero when idle" and never uses the micro apps name. The Azure September release notes did not carry it, and the Azure docs had no Genie App Builder page, when we checked on September 29.
- A micro app line on the pricing page. Not yet. The Databricks Apps pricing page still lists only Medium, Large and XLarge at 0.5, 1 and 3 DBU per hour; the only price for App Builder apps is the docs' no charge during Beta.
The September 2026 release notes, on a page that says releases are staged, now carry five Apps entries: the App Builder Beta on September 23 and horizontal scaling going generally available on September 29, plus telemetry and compliance-profile defaults on September 18 and tags for apps on September 25. Next we watch for a general availability date: neither what's-coming page lists App Builder or App Spaces yet.
Sources
- Databricks blog, June 16, 2026: Enabling Governed Vibe Coding for Enterprise Apps on Databricks
- Databricks docs, Beta: Genie App Builder (updated September 25, 2026) and App Spaces (updated September 28, 2026)
- Databricks docs: Databricks Apps, key concepts and Configure compute resources for a Databricks app
- Databricks pricing: Databricks Apps pricing and the pricing calculator
- Databricks docs: Horizontal scaling for Databricks apps, CLI apps commands, REST API, create an app, view app details and Lakebase with Databricks Apps
- Databricks platform release notes, AWS: June, July, August and September 2026, including the September 23 App Builder entry and the September 29 horizontal scaling entry
- What's coming: Databricks on AWS and Azure Databricks; Azure Databricks docs: horizontal scaling and September 2026 release notes
- Databricks, September 15, 2026: Databricks Apps for Everyone, transcript of the Data + AI Summit 2026 talk by Fabian Jakobs
- Databricks Apps product page and the docs sitemap, 6,027 URLs, for the absence checks
First checked September 16, 2026. Every quotation, rate and status above was re-checked on September 29, 2026 against the Databricks blog post, the 46 Databricks Apps docs pages including Genie App Builder and App Spaces, the CLI and REST API references, the June to September 2026 AWS platform release notes, the Azure September release notes, both what's-coming pages, the rendered Databricks Apps pricing page, the product page and the docs sitemap. Databricks can open a preview or publish a docs page without notice, as it did between our two checks, so read the Genie App Builder docs page before you plan around this. brickster.ai is an independent community project, not affiliated with, endorsed by, or sponsored by Databricks, Inc.



