Flexprice

We’re launching Customer Portal Theme Customization in Beta Today. When we launched customer portals in @tryflexprice last month, the core goal was simple: Give companies a clean and reliable way to show billing, usage, credit consumption and more to their customers. But one piece of feedback kept coming up. The customer portal worked well, but it still looked like it was out of brand. For many teams, especially those embedding the portal into their product or sharing it directly with customers, that matters. They want the experience to feel native to their brand, not like a third-party layer sitting on top. So we built theme customization for customer portals. You can now customize the portal to better match your brand using a few essential color codes. Once those are shared, we can configure the dashboard to align much more closely with your product’s visual identity. A small change on the surface, but an important one for teams that care deeply about customer experience and brand consistency. Now live in beta. Reach out to us if you're already using customer portals and would love to try this out! Join over 300+ industry stalwarts in our OSS community and build together : join.slack.com/t/flexpricecom…

Claude’s recent back to back updates made something very clear to me: Software is no longer meant only for humans. For years, SaaS products were designed around a predictable assumption. A human logs in, clicks around, and uses the product a few times a day. Pricing models were built around that behavior too. But with tools like Claude writing code, executing workflows and calling APIs autonomously, that assumption is breaking. Software is now being invoked by agents. An agent might run a workflow ten times in a minute. Or once in a week. It might spin up five tools for a single task and never touch them again. The usage pattern becomes bursty, unpredictable, and completely detached from the idea of “seats”. This changes how infrastructure needs to be built. Rate limits, entitlement checks, credit systems and billing logic now need to operate in real time. The system has to understand not just who the customer is, but what the agent is doing and how resources are being consumed. This is why traditional subscription models are starting to feel increasingly misaligned for AI-native products. When agents become the primary users of software, access-based pricing stops making sense. What matters instead is execution, consumption, and outcomes. The companies that recognize this shift early will design systems that are built for agents from day one. And the rest will spend the next few years slowly rewriting their billing infrastructure.

Introducing: Groups in Flexprice You can now organize prices (charges) and features into logical buckets such as Usage Pricing, Add-on Charges, GPU Costs, or AI Features and more in @tryflexprice As products evolve, pricing catalogs tend to become increasingly complex. Plans accumulate usage-based charges, feature entitlements, add-ons, and multiple pricing dimensions. Over time, this makes pricing harder to manage and invoices harder to interpret. Groups bring structure to that complexity. With Groups, you can assign both prices and features to a logical bucket. Once assigned, the grouping flows across the entire system. Invoice line items can be grouped, analytics can show usage and cost breakdown by group, and the customer portal can display usage categorized by group. This makes it easier for engineering, product, and finance teams to understand how pricing is structured and where revenue is coming from. We’ve also have a short demo from @sudeepsd_, showing how grouping work in practice. Docs: docs.flexprice.io/docs/product-c… Join our OSS Community and Get your Pricing Analyzed in Minutes : join.slack.com/t/flexpricecom…

Introducing: Flexprice Managed S3 Exports We’ve extended our S3 export workflow so teams can now use a Flexprice-managed S3 connection instead of always bringing their own AWS bucket and credentials This is a meaningful upgrade to the existing export system. Before this, S3 exports were powerful, but they assumed you were ready to manage: AWS buckets, IAM policies, Access keys, Regions, Storage setup and maintenance But many finance, ops and product teams simply want reliable exports for invoices, events, credit top-ups and credit usage, without turning reporting into an infrastructure task. With Flexprice-managed S3 connections, you now get: - No AWS account required - Zero bucket / IAM setup - Secure managed storage - Scheduled and manual exports For teams that want convenience, this makes exports much faster to start using. The broader goal stays the same: make monetization infrastructure reliable, fast to integrate, and compatible by default. Docs : #option-1-flexprice-managed-s3-connection" target="_blank" rel="nofollow noopener">docs.flexprice.io/docs/data-expo… Join our OSS community and get pricing feedback under hours: join.slack.com/t/flexpricecom…

Felt cute might delete later

Introducing Pricing Cookbooks in Flexprice Docs. We’ve seen this repeatedly: Teams understand their product, but struggle with how to structure pricing correctly from an infrastructure perspective. Should it be usage-based? Hybrid? Credit-based? Where do commitments fit? When do wallets make sense? So we created practical boilerplates, which we call cookbooks and we have started with the three most common monetization models: • Usage-based • Hybrid • Credit-based Each blueprint walks you through some of the biggest players in the industry and how they structure plans, configure charges, and set up billing in a way that actually works operationally, with a step-by-step guide to how to replicate the same in Flexprice as well. The goal is simple: Remove pricing architecture guesswork one step at a time. And if you’re using our recently launched MCP server, you can even replicate these setups directly by prompting your assistant to configure them for you by using the boilerplate as a reference! Docs are live - Usage-Based Pricing like Vapi: docs.flexprice.io/docs/boiler-pl… Credit-Based Pricing like Apollo: docs.flexprice.io/docs/boiler-pl… Hybrid Pricing like Resend: docs.flexprice.io/docs/boiler-pl… Join our community to connect with fellow builders: bit.ly/4huvkDm Happy Building!

You can now one-shot prompt your pricing infra! Introducing the Flexprice MCP Server. Connect Cursor, Claude Code, VS Code, Gemini, Windsurf and other supported MCP clients directly to your @tryflexprice dashboard and prompt your pricing! What does this mean for you? Every Flexprice API operation is exposed as a proper MCP tool letting your billing system be agent-operable in the most secure form. Your AI assistant can now: • Create subscriptions • Configure commitments • Issue invoices • Simulate usage events • Manage wallets and more, through structured tool calls. With agent-compatible billing infrastructure, non-technical founders can iterate. Finance can adjust contracts when needed. All by just prompting. One command to install. API-key authenticated. Check out this detailed demo where @sudeepsd_ one-shots a complex pricing structure and it gets done in a span of few minutes with the help of @claudeai. Docs : docs.flexprice.io/docs/connect/m… Join our OSS community today and connect with fellow builders: join.slack.com/t/flexpricecom…

_ _ _

@gauravvohra Hyped 👀

New drop tomorrow

There is a phase in every startup when building feels safe. Decisions are internal. Mistakes are inexpensive. If something breaks, you fix it quietly and move on. Then one day, that changes. There’s the public version, which occurs when everyone is watching, and you’re now under the scrutiny of eyes and questions, as if you’re being surrounded by paparazzi. It might be the first large customer. The first enterprise contract. The first serious invoice. Suddenly your system is no longer just code. It is revenue, commitments, and trust. From that moment on, building stops being private. Every architectural decision has external consequences. A billing assumption impacts someone’s financial reporting. An overlooked edge case becomes a customer escalation. This is EXACTLY where many teams realize that scale is not about handling more traffic. It is about handling more scrutiny. You cannot rely on speed alone. You cannot patch logic informally. The system must be predictable, explainable, and resilient under pressure. You stop asking, “Can we ship this quickly?” and start asking, “Will this still make sense six months from now?” That is when engineering becomes leadership. That's where carrying a straight face under pressure is important and that is the moment building stops being experimental and starts being real.

@SarvamAI the goat.

Indus by @SarvamAI approved. LFG!

Introducing: Reservation / Commitment Discounts 🎉 You can now enforce minimum usage or minimum spend on any metered charge with configurable overage premiums and optional true-up in Flexprice Built for AI, infra, APIs and usage-based billing orgs. A small 🧵 ↓

Docs are live : docs.flexprice.io/docs/subscript… Join Our Community to Connect with Fellow Builders: join.slack.com/t/flexpricecom… Happy Building!

You can configure per charge: • Minimum commitment (amount or quantity) • Overage factor (1.5× premium, 1.0× flat, 0.8× discount) • Optional true-up enforcement • Even windowed commitments (hourly buckets) This lets you guarantee revenue while still pricing usage dynamically. No spreadsheets. No custom logic. Fully enforced in billing. Here's a quick demo from our Founding Engineer!

It’s funny that @OpenAI has been simultaneously attempting to develop this entire workflow for credits and rate limiting internally while also collaborating with an external org. All of this, along with additional features mentioned in their recent blog, is already available in @tryflexprice :)

Wallets still store credits. Billing still happens in one base currency. Conversion rate simply defines the bridge between the two. Clean accounting and predictable invoices. Docs are live at : docs.flexprice.io/docs/wallet/co… Join Our Community to Connect with Fellow Builders: join.slack.com/t/flexpricecom…

We added two explicit controls: • conversion_rate — used when customers spend credits and when balances are shown in currency • topup_conversion_rate — optional rate used only when customers buy credits This lets you run bonus top-ups or discounted credit purchases without distorting how spending is calculated.

Introducing: Wallet Conversion Rate controls If you use credits or tokens for pricing, you need a clean way to define what 1 credit actually means in money. You can now configure how credits convert to base currency inside every wallet. A short 🧵 ↓