Looker Pricing 2026: Standard, Enterprise, Embed & AI Costs

Looker pricing has two layers: a platform subscription and user licensing. Google publishes the structure and included entitlements but no numeric list prices for Standard, Enterprise, Embed, Developer, Standard or Viewer users. All three platform editions use sales-led annual commitments and currently include 10 Standard users plus 2 Developer users.

Two-part pricing model

Google divides Looker Core pricing into platform pricing and user pricing.

The platform fee covers the Looker instance, administration, integrations and semantic-modeling capabilities.

User pricing covers individual Developer, Standard and Viewer licenses beyond what is included with the platform.

Neither layer has a public numeric list price, so buyers need a formal quote before comparing total cost.

Standard edition

Standard is intended for small organizations or teams with fewer than fifty users.

It includes one production instance, ten Standard users, two Developer users and upgrades.

Current API allowances are up to one thousand query-based and one thousand administrative calls per month.

Pricing requires an annual sales quote rather than a public monthly rate.

Enterprise edition

Enterprise includes one production instance, ten Standard users and two Developer users.

It adds enhanced security capabilities and increases current API allowances to one hundred thousand query-based calls and ten thousand administrative calls per month.

This edition is aimed at larger internal BI and analytics deployments.

Final cost depends on the platform quote plus additional user licensing and any related services.

Embed edition

Embed is designed for deploying analytics inside external applications and customer experiences.

It includes one production instance, ten Standard users and two Developer users.

Current API allowances rise to five hundred thousand query-based calls and one hundred thousand administrative calls per month.

Embedding scale, users, API volume and professional services can all affect final contract value.

Annual subscription terms

Google's current pricing documentation says annual Looker subscriptions are available in one-, two- and three-year terms.

Public pages do not publish a numeric discount for longer commitments.

Organizations should request quote comparisons for different term lengths rather than assuming a standard percentage reduction.

Renewal, termination and refund rights should be read directly from the order form.

Included users

Each current Looker Core platform edition includes ten Standard users and two Developer users.

These included seats matter when comparing quotes because they are bundled into the platform subscription rather than added separately.

Additional Standard, Developer or Viewer licenses can increase the cost.

Ask the seller to show platform and incremental-user pricing separately.

Developer users

Developer licenses are for users who need LookML development, administration, SQL Runner, API and broader modeling privileges.

These are typically analytics engineers, BI developers and platform administrators.

Developer access is more capable than Standard or Viewer access and is therefore an important part of user-mix planning.

Do not assign developer privileges broadly if users only consume or explore governed content.

Standard users

Standard users can access dashboards, Looks, Explore, SQL Runner and scheduling without full LookML development or administration privileges.

They can create and save content within the governed semantic model.

Standard is the appropriate class for many analysts and advanced business users.

Ten Standard users are included with each platform edition before incremental licensing.

Viewer users

Viewer users primarily consume folders, boards, dashboards and Looks.

Google does not publish a numeric Viewer price.

Large read-only audiences can therefore make early budget comparison difficult without a quote.

Provide expected creator, analyst and viewer counts to sales so the total contract reflects the actual audience mix.

90-day trial

Looker Core supports trial Standard, Enterprise and Embed instances for ninety days.

The trial mirrors the relevant edition's feature support closely enough to validate modeling, query performance and application patterns.

A trial cannot be converted directly into a paid non-trial instance.

Production migration therefore requires a new instance and content import, which should be included in implementation planning.

Conversational Analytics promotional period

Google's current pricing page says Looker Conversational Analytics remains in a promotional period without quota limits or overage fees, subject to fair use.

This supersedes the older Toollers snapshot that treated October 1, 2026 as the start of enforced overage billing.

Google says it will provide at least ninety days of formal notice before billing and quota enforcement begin.

Organizations should use the current period to measure token consumption.

Standard AI token allocation

Google currently publishes a future monthly Standard allocation of sixty million input data tokens and 1.2 million output data tokens.

Unused future allocations are not expected to roll over once enforcement begins.

The allocation is pooled at the instance level across authenticated users.

During the current promotional period, Google says quota limits and overage fees are not enforced.

Enterprise and Embed AI allocations

Enterprise or Advanced is currently documented with a future monthly allocation of three hundred million input and six million output data tokens.

Embed or Elite is documented with 1.2 billion input and twenty-four million output tokens.

Non-production and add-on instances receive smaller baseline allocations.

These published numbers help buyers model future AI usage even though enforcement is postponed.

Future overage rates

Google publishes future overage rates of $3 per one million input data tokens and $20 per one million output data tokens.

Those rates apply after included allocations once billing enforcement actually begins.

They should not be represented as a currently active October 10, 2026 charge because Google has extended the promotional period.

Procurement should monitor Google Cloud notices for the future enforcement date.

API scale as a cost driver

Edition choice changes API allowances substantially.

Standard provides 1,000 query and 1,000 administrative calls monthly; Enterprise raises those limits to 100,000 and 10,000; Embed reaches 500,000 and 100,000.

Applications with heavy automation or embedding should not choose Standard only because the user count is small.

API demand can be a more important edition requirement than headcount.

Google Cloud consumption

Looker queries the underlying data platform, so BigQuery, Cloud SQL, Snowflake or other warehouse costs remain separate from the Looker subscription.

High query volume, inefficient models and conversational analytics can increase warehouse consumption.

Google Cloud networking and related infrastructure can also add cost depending on architecture.

Total BI cost therefore includes both Looker and the data platform underneath it.

Professional services and migration

Complex LookML modeling, embedded analytics and enterprise migrations can require internal engineering or external consulting.

Those services are not represented by the platform quote alone.

Trial-to-production migration also creates implementation work because a trial instance cannot simply be upgraded in place.

Ask for implementation responsibilities and professional-services scope separately from recurring subscription pricing.

Looker versus Power BI

Power BI publishes a Free account, Pro at $14 per user/month paid yearly and Premium Per User at $24.

That makes Power BI much easier to budget for small and mid-sized teams.

Looker differentiates with LookML semantic governance and deeper Google Cloud alignment.

Choose based on whether transparent seat economics or centralized semantic modeling is more important.

Looker versus Tableau

Tableau Cloud Standard publishes Creator at $75, Explorer at $42 and Viewer at $15 per user/month billed annually.

Tableau therefore provides clearer upfront role pricing.

Looker has stronger code-centric semantic governance, while Tableau emphasizes visual exploration and cross-platform authoring.

The final Looker quote should be compared with the complete Tableau Creator/Explorer/Viewer mix.

Looker versus Qlik Sense

Qlik Cloud Analytics currently starts at $300/month for Starter, $825 for Standard and $2,750 for Premium, billed annually; Enterprise is custom.

Qlik's larger plans increasingly use data-for-analysis capacity rather than user pricing.

Looker uses platform plus user licensing and relies heavily on the underlying warehouse.

Compare both user population and data workload before judging total cost.

Looker versus ThoughtSpot

ThoughtSpot's current Analytics pricing starts around $25 per user/month for Essentials and $50 per user/month for Pro on its user-based model, while Enterprise is custom.

ThoughtSpot emphasizes search and agentic analytics, with some plans also offering usage pricing.

Looker emphasizes governed semantic modeling through LookML.

Teams should compare whether AI-first self-service or code-governed metrics is the primary objective.

Pricing recommendation

Request a Looker quote early because platform and user list prices are not public.

Provide the expected Standard, Developer and Viewer mix, edition, API volume, embedding requirements, trial plan and AI usage assumptions.

Ask Google to separate recurring platform fees, incremental user pricing and implementation services.

Treat the published token rates as future rates while the current promotional no-overage period remains in force.

Pricing analysis: Semantic-layer ownership

Looker works best when one accountable data team owns LookML models, business definitions and reusable dimensions. Without clear ownership, the semantic layer can accumulate duplicate fields and conflicting interpretations even though the platform is designed to prevent that problem.

Define model maintainers, code-review rules and deprecation processes before self-service adoption grows.

Pricing analysis: LookML learning curve

LookML gives analytics engineers a software-development workflow for business logic, but that strength creates a training requirement. Teams without SQL, Git and modeling experience may take longer to become productive than they would with a purely visual BI tool.

Budget onboarding for developers and document the project's naming, join and measure conventions.

Pricing analysis: Query performance

Looker sends queries to the underlying database rather than replacing the warehouse. Poor SQL, large joins, weak partitioning or inefficient warehouse design can therefore surface as slow dashboards.

Test representative production queries and use aggregate tables, persistent derived tables and warehouse optimization where appropriate before assuming the BI layer is the only bottleneck.

Pricing analysis: Conversational analytics governance

Gemini-powered Conversational Analytics can make governed metrics easier to access, but natural-language output should still be evaluated against known answers. Good model descriptions, field labels and semantic definitions directly improve the quality of the experience.

Organizations should decide which models are appropriate for AI access and who reviews generated answers before they are used for high-impact decisions.

Pricing analysis: Token monitoring

Google currently keeps Looker Conversational Analytics in a promotional no-overage period, while publishing future token allocations and overage rates. This creates a useful window to measure actual usage before billing enforcement begins.

Use the available system activity and observability data to estimate future token consumption rather than assuming the included allocation will always be enough.

Pricing analysis: Embedding architecture

Looker Embed is designed for external analytics and custom applications, but embedding adds authentication, tenancy, theming, API and product-engineering requirements.

Prototype one real customer workflow before committing to an embedded architecture so the team understands both platform cost and engineering effort.

Pricing analysis: API planning

API limits differ dramatically across Standard, Enterprise and Embed. Standard is suitable for smaller internal use, while higher editions provide much larger query and administrative API allowances.

If analytics is being integrated deeply into operational workflows, estimate API volume early so an edition change does not become a late procurement surprise.

Pricing analysis: Security design

Looker on Google Cloud supports mature controls such as IAM, private connectivity options, VPC Service Controls and customer-managed encryption in eligible editions. Those capabilities still require thoughtful configuration around users, groups, service accounts and network boundaries.

Security architecture should be designed alongside LookML governance rather than treated as a post-launch administration task.

Pricing analysis: Trial migration

The 90-day Looker Core trial is useful for proving models and performance, but Google documents that trial instances cannot be upgraded directly into paid production instances. A new paid instance must be created and content imported.

Plan the proof of concept with that migration step in mind so production cutover is not treated as a simple license toggle.

Pricing analysis: Decision framework

Compare Looker and alternatives on semantic governance, analyst workflow, visualization, AI, embedded capabilities, ecosystem fit and total three-year cost.

The best platform is the one that keeps metrics trustworthy while still giving the intended audience enough self-service access.

Pricing analysis: Semantic-layer ownership

Looker works best when one accountable data team owns LookML models, business definitions and reusable dimensions. Without clear ownership, the semantic layer can accumulate duplicate fields and conflicting interpretations even though the platform is designed to prevent that problem.

Define model maintainers, code-review rules and deprecation processes before self-service adoption grows.

Pricing analysis: LookML learning curve

LookML gives analytics engineers a software-development workflow for business logic, but that strength creates a training requirement. Teams without SQL, Git and modeling experience may take longer to become productive than they would with a purely visual BI tool.

Budget onboarding for developers and document the project's naming, join and measure conventions.

Continue reading about Looker

• Looker tool profile
• Looker Review: Features, Pricing, Pros and Cons
• Looker Alternatives 2026: 4 BI Platforms by Use Case