<!-- mobian-agent-page publisher="dailydev" canonical="https://daily.dev/posts/smarter-cost-controls-for-serverless-ftw6usfpi" -->

---
title: Smarter cost controls for serverless | daily.dev
description: Databricks is bringing classic compute's cost controls to serverless compute for notebooks, jobs, and pipelines. Serverless usage has grown more than 3x in the...
canonical: https://daily.dev/posts/smarter-cost-controls-for-serverless-ftw6usfpi
twitter:card: summary_large_image
twitter:site: @dailydotdev
og:type: website
og:site_name: daily.dev
og:title: Smarter cost controls for serverless | daily.dev
og:description: Databricks is bringing classic compute's cost controls to serverless compute for notebooks, jobs, and pipelines. Serverless usage has grown more than 3x in the...
og:url: https://daily.dev/posts/smarter-cost-controls-for-serverless-ftw6usfpi
og:image: https://api.daily.dev/og/posts/FtW6USfPI.png
og:image:alt: Smarter cost controls for serverless
og:image:width: 1200
og:image:height: 630
og:locale: en
---

> ## Documentation Index
> Fetch the complete documentation index at: https://daily.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Smarter cost controls for serverless

**[databricks](https://daily.dev/sources/databricks)** · 5 min read · 0 upvotes · 0 comments

## Summary

Databricks is bringing classic compute's cost controls to serverless compute for notebooks, jobs, and pipelines. Serverless usage has grown more than 3x in the past year. Three tools now mirror what classic compute offered: tags for attribution, entitlements for access control, and rate limits for spend caps. Serverless Compute Access Controls is generally available now, letting admins restrict who can run serverless via Can Use and Can Manage permissions. Tags for attribution and rate limits are both in Beta. A new serverless_compute_id field in system.billing.usage lets teams track cost per compute object.

## Full article

daily.dev links to this article rather than hosting it. Read it at the original source: <https://www.databricks.com/blog/smarter-cost-controls-serverless>

## Questions this post answers

### How do I control who can use serverless compute in Databricks?

Use Serverless Compute Access Controls, which is generally available. Every serverless compute object supports two permissions, Can Use and Can Manage, the same model used for SQL warehouses. Admins open the Compute page, go to the Serverless tab, remove 'All Users' from a default compute object, and add a specific group; everyone starts with Can Use by default so nothing changes until an admin acts.

_Platform teams locking down serverless access can track rollout details like this on daily.dev._

### How can I attribute Databricks serverless compute costs by team?

Tag the serverless compute object, and every DBU it runs carries that tag through to billing in the system.billing.usage table, broken out by user, product, and tag. This serverless compute tagging feature is in Beta. A new serverless_compute_id field also attributes spend per compute object, making 'cost by compute object' as easy as 'cost by team'.

_Teams building cost dashboards for serverless workloads can follow updates like this on daily.dev._

### Can I set spend limits on Databricks serverless compute like I would with cluster size on classic compute?

Yes, Rate Limits bring spend caps to serverless compute objects and are now available in Beta, enabled through Databricks preview settings. For notebooks and jobs, the size you pick is a maximum autoscaling ceiling rather than a fixed size, so choosing XL for a job that only needs Medium results in Medium being allocated.

_Anyone budgeting serverless workloads can watch for rate-limit changes like this on daily.dev._

## Similar posts on daily.dev

- [The Evolution of Data Engineering: How Serverless Compute is Transforming Notebooks, Lakeflow Jobs, and Spark Declarative Pipelines](https://daily.dev/posts/the-evolution-of-data-engineering-how-serverless-compute-is-transforming-notebooks-lakeflow-jobs--rvifjtpho) · databricks · 0 upvotes · 0 comments
- [Amazon EMR Serverless adds support for job run level cost allocation](https://daily.dev/posts/amazon-emr-serverless-adds-support-for-job-run-level-cost-allocation-is911btkj) · AWS · 1 upvotes · 0 comments
- [Budgets, Quotas, and Monitors: The Cost Controls I Map Before Agents Go Wider](https://daily.dev/posts/budgets-quotas-and-monitors-the-cost-controls-i-map-before-agents-go-wider-czhweo7rq) · Snowflake Community · 1 upvotes · 0 comments
- [How the 5 major cloud data warehouses really bill you: A unified, engineer-friendly guide](https://daily.dev/posts/how-the-5-major-cloud-data-warehouses-really-bill-you-a-unified-engineer-friendly-guide-i6rrkzrg1) · ClickHouse · 2 upvotes · 0 comments
- [How to Approach Data Warehouse Cost Management at Scale](https://daily.dev/posts/how-to-approach-data-warehouse-cost-management-at-scale-zlk0gxety) · finout · 0 upvotes · 0 comments

---

Tags: [#cloud](https://daily.dev/tags/cloud), [#serverless](https://daily.dev/tags/serverless), [#databricks](https://daily.dev/tags/databricks), [#finops](https://daily.dev/tags/finops)

[View this post on daily.dev](https://daily.dev/posts/smarter-cost-controls-for-serverless-ftw6usfpi)

```json
{"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]}
{"@context":"https://schema.org","@type":"TechArticle","headline":"Smarter cost controls for serverless","url":"https://daily.dev/posts/smarter-cost-controls-for-serverless-ftw6usfpi","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/smarter-cost-controls-for-serverless-ftw6usfpi"},"datePublished":"2026-10-29T15:20:05.214Z","dateModified":"2026-10-29T15:23:01.892Z","description":"Databricks is bringing classic compute's cost controls to serverless compute for notebooks, jobs, and pipelines. Serverless usage has grown more than 3x in the...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/6dd06542b63c817848bc454308daaabb?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/6dd06542b63c817848bc454308daaabb?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"databricks","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"databricks","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/fa7aa720f2db4d1eba826814730482c8","url":"https://daily.dev/sources/databricks"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/smarter-cost-controls-for-serverless-ftw6usfpi","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"cloud,serverless,databricks,finops","timeRequired":"PT5M"}
{"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"databricks","item":"https://daily.dev/sources/databricks"},{"@type":"ListItem","position":3,"name":"Smarter cost controls for serverless"}]}
{"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/smarter-cost-controls-for-serverless-ftw6usfpi#faq","mainEntity":[{"@type":"Question","name":"How do I control who can use serverless compute in Databricks?","acceptedAnswer":{"@type":"Answer","text":"Use Serverless Compute Access Controls, which is generally available. Every serverless compute object supports two permissions, Can Use and Can Manage, the same model used for SQL warehouses. Admins open the Compute page, go to the Serverless tab, remove 'All Users' from a default compute object, and add a specific group; everyone starts with Can Use by default so nothing changes until an admin acts. Platform teams locking down serverless access can track rollout details like this on daily.dev."}},{"@type":"Question","name":"How can I attribute Databricks serverless compute costs by team?","acceptedAnswer":{"@type":"Answer","text":"Tag the serverless compute object, and every DBU it runs carries that tag through to billing in the system.billing.usage table, broken out by user, product, and tag. This serverless compute tagging feature is in Beta. A new serverless_compute_id field also attributes spend per compute object, making 'cost by compute object' as easy as 'cost by team'. Teams building cost dashboards for serverless workloads can follow updates like this on daily.dev."}},{"@type":"Question","name":"Can I set spend limits on Databricks serverless compute like I would with cluster size on classic compute?","acceptedAnswer":{"@type":"Answer","text":"Yes, Rate Limits bring spend caps to serverless compute objects and are now available in Beta, enabled through Databricks preview settings. For notebooks and jobs, the size you pick is a maximum autoscaling ceiling rather than a fixed size, so choosing XL for a job that only needs Medium results in Medium being allocated. Anyone budgeting serverless workloads can watch for rate-limit changes like this on daily.dev."}}]}
```

