docs(pricing-may-2026): May 21, 2026 pricing + packaging launch#119
Open
hongyi-chen wants to merge 3 commits into
Open
docs(pricing-may-2026): May 21, 2026 pricing + packaging launch#119hongyi-chen wants to merge 3 commits into
hongyi-chen wants to merge 3 commits into
Conversation
Umbrella tracker for the May 21, 2026 pricing and packaging docs launch. Populates as the three thematic PRs land: - #114 - Credits, billing, and cloud-agent team billing - #115 - BYOK + custom inference endpoint + BYOLLM - #116 - Plans summary, pricing FAQs, teams copy Co-Authored-By: Oz <oz-agent@warp.dev>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
|
I'm starting a first review of this pull request. You can view the conversation on Warp. I completed the review and no human review was requested for this pull request. Comment Powered by Oz |
…LLM) (#115) * docs(pricing-may-2026): customer-supplied inference (BYOK + CIE + BYOLLM) Part of the May 14, 2026 pricing-and-packaging docs launch. - BYOK is now available on the Free plan; page rewritten to open eligibility, refresh model examples, and add the BYOK/CIE/BYOLLM comparison table. - New Custom Inference Endpoint (CIE) page for OpenAI Chat Completions– compatible endpoints (OpenRouter, LiteLLM, z.ai, internal gateways). Sidebar entry added under Plans and billing. - BYOLLM reframed as Enterprise-only managed inference. AWS Bedrock GA; Google Vertex AI and Azure AI Foundry on the roadmap. Cloud-native credentials now span IAM/OIDC across all three cloud providers. - 10-employee org rule applies to BYOK and CIE; larger orgs need Business or Enterprise. - Platform-credits caveats: on Business/Enterprise local agent runs, customer-supplied inference still consumes platform credits even though no AI credits are charged. - plans-and-billing/index.mdx updated to surface the new CIE page. Co-Authored-By: Oz <oz-agent@warp.dev> * docs(pricing-may-2026): note July 1 self-serve preview period in BYOK + CIE platform-credits callouts Both BYOK and CIE pages now spell out that self-serve billing for platform credits (including Business BYOK / CIE) doesn't start until July 1, 2026. Between May 14 and June 30, 2026, platform-credit consumption is visible in the Warp app's usage breakdown for transparency on Build, Max, and Business, but no platform credits are deducted from your Reload pool or counted against your spend cap. Enterprise plans are billed per contract from May 14 and aren't affected by this preview period. Co-Authored-By: Oz <oz-agent@warp.dev> * docs(pricing-may-2026): correct launch date May 14 \u2192 May 21, 2026 Co-Authored-By: Oz <oz-agent@warp.dev> * docs(pricing-may-2026): revert BYOLLM page to main, keep changes minimal Per launch direction: keep the Enterprise BYOLLM page largely unchanged for this launch. The BYOK/CIE/BYOLLM comparison still lives on the BYOK and CIE pages, so readers landing on either of those will see the three-way framing. This restores: - The original AWS-Bedrock-focused frontmatter description and opening paragraph (instead of the cross-provider reframing). - The original 'BYOLLM currently supports AWS Bedrock only. Coming soon: Azure Foundry and Google Vertex support.' caveat. - The original 'Cloud-native credentials - Authenticate using each user's AWS IAM identity' key feature. - The original 'How is BYOLLM different from BYOK?' FAQ with its 4-row comparison table. - The original Related resources list. Drops the launch-era additions: - The 'How BYOLLM differs from BYOK and Custom inference endpoint' section with the three-way comparison table. - The :::note about centrally configured BYOK / CIE for Enterprise being a fast-follow. - The :::note about platform credits for BYOLLM-routed local runs. Co-Authored-By: Oz <oz-agent@warp.dev> * docs(pricing-may-2026): drop CIE abbreviation, narrow credit claims, remove preview-period notes, restore File locations sidebar - Restore the 'File locations' sidebar entry under Settings file (added on main by PR #110, accidentally dropped during the rebase). - Drop the 'CIE' abbreviation throughout the customer-supplied inference pages. Use the full name 'custom inference endpoint' (or 'your endpoint' / 'endpoint-routed model' in context) instead. - Narrow the 'never consumes Warp credits' claim to 'doesn't consume AI credits' on the BYOK and custom inference endpoint pages, since Business / Enterprise local agent runs still consume platform credits. - Rewrite the 'No Warp credits consumed' Key features bullet on the custom inference endpoint page so it accurately calls out the platform-credits caveat on Business / Enterprise. - Drop the 'Self-serve preview period' paragraph from the platform-credits :::note callouts on the BYOK and custom inference endpoint pages. The July 1, 2026 cutover lives only in pricing-faqs.mdx now \u2014 canonical feature pages don't carry the launch-period detail. Co-Authored-By: Oz <oz-agent@warp.dev> * docs(pricing-may-2026): de-emphasize billing in BYOK + custom inference endpoint openings, consolidate plan notes - Reframe the BYOK and custom inference endpoint opening copy around model selection and data routing instead of billing. Move the AI-credits-consumption details out of the intro and down into the dedicated billing sections where they belong. - Collapse the two stacked :::note callouts about plan availability and the 10-or-fewer-employees rule into a single, briefer note on each page. - Move the Business / Enterprise platform-credits caveat off the top of the BYOK page and into the 'Credit usage' subsection alongside the related credit details. - Trim the 'BYOK on Enterprise and Business plans' section on the BYOK page so it doesn't restate the org-size rule already covered up top. - Replace the redundant 'Plan availability' section on the custom inference endpoint page with a focused 'Centrally managed configuration' section that only covers what's still unique to that page (user-level config today, admin-managed coming later).\n - Light copy polish on phrasing in both files. Co-Authored-By: Oz <oz-agent@warp.dev> * docs(pricing-may-2026): restore original BYOK opening, narrow only the credits claim to AI credits Per follow-up review, undo the polish on the BYOK intro and restore the original three-paragraph opening verbatim: - Title back to 'Bring Your Own API Key' (Title Case) - 'Warp supports Bring Your Own Key (BYOK) for users who want to connect Warp's agents to their own Anthropic, OpenAI, or Google API accounts.' - 'This lets you use your own API keys to access models directly, giving you full control over model selection, billing, and data routing. See Model Choice for a list of supported models.' - 'BYOK provides greater flexibility in model access and ensures Warp never consumes your AI credits for requests routed through your own keys.' The only substantive change vs the original is narrowing 'credits' to 'AI credits' in that last sentence, per earlier feedback that the unqualified 'never consumes Warp credits' claim is too broad now that Business / Enterprise local runs can consume platform credits. The combined plan-availability + 10-employee :::note below the intro stays as-is. Everything below the intro (BYOK works, Enabling BYOK, billing behavior, Credit usage with the platform-credits note, ZDR, Enterprise/Business config, Related resources) is unchanged. Co-Authored-By: Oz <oz-agent@warp.dev> * docs(pricing-may-2026): soften absolute 'no AI credits / 0 credits' claims in BYOK + CIE credit sections - Drop the 'No AI credits are consumed' bullet and the 'credit transparency footer shows 0 credits used' sentence from BYOK's Credit usage subsection. Replaced with a more general framing that says inference is billed through your provider account rather than drawing from your Warp AI credits, alongside the existing platform credits caveat for Business / Enterprise. - Same softening on the custom inference endpoint page's Warp AI credits subsection \u2014 collapse the three firm bullets into one general sentence and keep the platform-credits note. This avoids the misleadingly absolute '0 credits' claim, which is inaccurate for Business / Enterprise local runs where platform credits can still apply. Co-Authored-By: Oz <oz-agent@warp.dev> * docs(pricing-may-2026): reframe custom inference endpoint intro to lead with powering Warp's agents Mirror the BYOK page's intro pattern so it's explicit upfront that a custom inference endpoint is used to power Warp's agents. New opening: Warp supports custom inference endpoints for users who want to power Warp's agents with any OpenAI-compatible inference endpoint \u2014 a model router, hosted gateway, or internal infrastructure they already run. This lets you route AI requests through your preferred provider, run inference behind your own gateway, or use a router like OpenRouter or LiteLLM, while keeping the agent experience inside Warp. No other changes. Co-Authored-By: Oz <oz-agent@warp.dev> * Cleanup pass: BYOK acronym + BYOLLM table scope - bring-your-own-api-key.mdx intro: fix the wrong BYOK expansion ('Bring Your Own Key (BYOK)') to match the page title and standard usage ('Bring Your Own API Key (BYOK)'). - bring-your-own-api-key.mdx + custom-inference-endpoint.mdx comparison tables: tighten the BYOLLM row so it reflects current launch scope ('AWS Bedrock today; Azure Foundry and Google Vertex coming soon') instead of implying all three ship at launch. Co-Authored-By: Oz <oz-agent@warp.dev> * PR #115 review: address Tyler's comments - bring-your-own-api-key.mdx 'Platform credits' note: Tyler correctly pointed out that platform credits also apply for cloud agent runs. Rewrite the line to lead with the cloud-agent case ('apply to every cloud agent run on any plan') and then cover the local-runs case ('and to local agent runs on Business and Enterprise when using BYOK, a custom inference endpoint, or BYOLLM'). - bring-your-own-api-key.mdx 'How BYOK works' opening: drop the misleading 'directly to the model provider' phrasing since requests still flow through Warp's infrastructure. Now reads 'Warp uses these API keys when routing your agent requests to the model provider you've configured.' Tyler's third comment was a stylistic preference for 'need' over 'require' on the page note, which already uses 'need' here. The parallel 'require' phrasing in pricing-faqs.mdx will be normalized on PR #116. Co-Authored-By: Oz <oz-agent@warp.dev> --------- Co-authored-by: Oz <oz-agent@warp.dev>
![oz-for-oss[bot]](https://avatars.githubusercontent.com/in/3450139?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Overview
This PR is described as an umbrella merge for the May 21, 2026 pricing and packaging docs launch. The attached annotated diff is empty, so there are no changed files or commentable lines to review in this run.
Concerns
- No issues found in the provided diff.
Verdict
Found: 0 critical, 0 important, 0 suggestions
Approve
Comment /oz-review on this pull request to retrigger a review (up to 3 times on the same pull request).
Powered by Oz
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Umbrella tracker for the May 21, 2026 pricing and packaging docs launch. This PR collects the three thematic PRs targeting
hyc/plan-updates; merging this one lands the full launch intomain.Thematic PRs landing here first
This PR currently has just a seed empty commit and will populate as the three thematic PRs are merged.
Conversation: https://staging.warp.dev/conversation/751e9577-89d8-47d6-8271-3f0421b7714d
Co-Authored-By: Oz oz-agent@warp.dev