A billing ledger on Postgres, tested with randomized invariants

Hi HN, James, Valter, Sam and the team from ElectricSQL here. We're really excited to be sharing ElectricSQL with you today. It's an open source, local-first sync layer that can be used to build reactive, realtime, offline-capable apps directly on Postgres with two way active-active sync to SQLite (including with WASM in the browser). Electric comprises a sync layer (built with Elixir) placed in front of your Postgres database and a type safe client that allows you to bidirectionally sync data from your Postgres to local SQLite databases. This sync is CRDT-based, resilient to conflicting…

Yo. OtterTune is a database optimization service. It uses machine learning to automatically tune your MySQL and Postgres configuration (i.e., RDS parameter groups) to improve performance and reduce costs. It does this by only looking at your database's runtime metrics (e.g., INNODB_METRICS, pg_stat_database, CloudWatch). We don't need to examine sensitive queries or user tables. We spun this project out of my research group at Carnegie Mellon University in 2020. This week we've announced that OtterTune is now available to the public. We are offering everyone a starter account to try it out…

Hey HN, stripe-no-webhooks is an open-source library that syncs your Stripe payments data to your own Postgres database: https://github.com/pretzelai/stripe-no-webhooks. Here's a demo video: https://youtu.be/cyEgW7wElcs Why is this useful? (1) You don't have to figure out which webhooks you need or write listeners for each one. The library handles all of that. This follows the approach of libraries like dj-stripe in the Django world (https://dj-stripe.dev/). (2) Stripe's API has a 100 rpm rate limit. If you're checking subscription status…

Self-hosted Next.js 15 boilerplate: OAuth 2.1 + PKCE, API key management, Stripe usage-based billing with explicit metering decisions, Redis rate limiting. 300 tests. No revenue share. https://mcp-billing.com

AI-native billing & payments for usage-based AI products

Hey HN! I'm the founder of Credyt (https://credyt.ai). If you're running an AI product that burns $0.50+ per interaction, you need to bill customers as usage happens, not at the end of the month. Otherwise you're a bank for your customers, and you'll run out of money before they do. Why invoice-based billing doesn't work for AI: Most usage-based billing tools (Stripe Billing, Orb, etc.) were built for SaaS. They meter usage all month, then send an invoice. That works fine when your COGS is 5%. It's a disaster when you're paying your AI vendor upfront for every request and your…