Flexprice 讓 AI 原生與 SaaS 團隊能以使用量為基礎、信用為基礎及混合定價模式,進行即時計量與報告,並隨產品演進而擴展。
AI 翻譯
Flexprice lets AI-native and SaaS teams operate usage-based, credit-based, and hybrid pricing with real-time metering and reporting that scales as your product evolves
金融Go · ShellGitHub @flexprice上線中營運者未確認
試用過了嗎? 點一下就好,不需要登入。
基於使用量的定價與計費,供開發者使用 🔓 雲端或自行託管 ⚙️ 無程式碼 UI 💰 即時使用量計量 🎟 點數與充值 🔑 控制功能存取
AI 翻譯
Usage-based pricing and billing for developers 🔓 Cloud or self-hosted ⚙️ No-code UI 💰 Realtime usage metering 🎟 Credits & top-ups 🔑 Control feature access
取自儲存庫 README
正在載入完整 README。
檢視完整 README ↗Docs • Demo • Website • LinkedIn • X • Slack Community
The Flexprice core (metering, credits, pricing, billing) has an open and composable design.
Your application, whether it's running backend APIs, AI agents, or custom workflows, can send usage data to Flexprice. You can directly stream data from data warehouses or analytics pipelines as well.
At the core, Flexprice processes this data in real time. We handle everything that usually ends up as custom logic built by developers. Our platform calculates pricing based on the customer’s plan, applies any prepaid or promotional credits, enforces feature limits, and generates accurate invoices automatically. Whether you're using seat-based subscriptions, usage-based pricing, or prepaid credit bundles, you can set up and iterate on your pricing model without writing billing infrastructure from scratch.
After billing is computed, our platform connects to your existing tools for payments, CPQ, CRM, and accounting, ensuring billing information flows into the systems your business already uses. It can sync invoices to your payment processor, update customer data in your CRM, and push revenue numbers to your accounting tools.
With this architecture, you get full control over how billing works inside your product, while saving your team from the complexity of maintaining it all.
When existing billing tools don’t flex to your product’s needs, developers shoulder the burden eating up valuable development time and causing ongoing maintenance headaches.
Modern app developers often find themselves wrestling with billing systems. Here are some of the biggest pain points that turn billing into a “developer problem”:
Rigid billing tools (lack of flexibility): Traditional billing services handle simple subscriptions or payments, but anything beyond that – usage metering, credit systems, feature gating, custom invoice logic – usually isn’t supported out of the box. Developers end up writing countless workarounds or custom code to accommodate these needs. In other words, if your pricing model doesn’t fit the tool, you’re stuck bending your product or building logic from scratch.
Complex usage metering at scale: Implementing accurate usage tracking is hard. It involves capturing high-volume events, aggregating them in real time, handling edge cases (prorations, time zones, etc.), and ensuring it all works reliably at scale. Few teams anticipate how many moving parts this requires until they’re deep in the weeds of building it.
Vendor lock-in and black boxes: Relying on third-party billing platforms can mean surrendering flexibility. Many SaaS billing providers are closed systems or charge a percentage fee on revenue, which frustrates engineers who want full control over their pricing logic and data. Changing providers later can be a massive undertaking, so teams feel “stuck” with a less-than-ideal solution.
Delayed monetization & opportunity cost: Every week spent building or patching a billing system is a week not spent on core product features. If it takes months to implement a new pricing model or usage-based feature, that’s delayed revenue and lost agility for the business. What might be scoped as a “quick two-month project” can quickly spiral into a multi-year maintenance headache, tying up engineering resources and slowing time-to-market for new offerings.
Flexprice’s approach is to abstract away the hard parts of billing while preserving maximum flexibility and transparency for developers. It addresses the above pain points in several key ways:
By handling the heavy lifting from real-time usage tracking to invoice generation, Flexprice lets your team focus on building your actual product, not the billing system around it
Flexprice provides a rich set of features to power usage-based and hybrid billing models. Key features include:
Each of these features is accessible via Flexprice’s APIs and dashboard, allowing you to mix and match to build the exact billing experience you need.
To run Flexprice for local development or running from source, you will need
The easiest way to get started is using our Docker Compose setup:
# Clone the repository
git clone https://github.com/flexprice/flexprice
cd flexprice
# Set up the complete development environment
make dev-setup
This will:
Once complete, you can access:
# Restart only the FlexPrice services
make restart-flexprice
# Stop all services
make down
# Clean everything and start fresh
make clean-start
# Build the FlexPrice image separately
make build-image
# Start only the FlexPrice services
make start-flexprice
If you prefer to run the application directly:
# Start the required infrastructure
docker compose up -d postgres kafka clickhouse redis temporal temporal-ui
# Run the application locally
go run cmd/server/main.go
Whether you're a newbie coder or a wizard 🧙♀️, your perspective is golden. Take a peek at our:
Flexprice is a commercial open source company, which means some parts of this open source repository require a commercial license. The concept is called "Open Core" where the core technology (99%) is fully open source, licensed under AGPLv3 and the last 1% is covered under a commercial license ([ee , internal/ee Enterprise Edition]).
[!TIP] We work closely with the community and always invite feedback about what should be open and what is fine to be commercial. This list is not set and stone and we have moved things from commercial to open in the past. Please open a discussion if you feel like something is wrong.