Update

Product Introduction

1. Update is a developer toolkit that provides pre-built infrastructure components for adding user authentication, subscription billing, and access control to web applications. It offers SDKs and CLI tools that integrate with existing services like Supabase and Stripe through a unified API layer. Developers can implement production-ready billing systems and permission models in minutes using native framework integrations for Next.js, React, and Node.js.

2. The core value lies in eliminating 90% of boilerplate code required for multi-tenant SaaS systems by combining authentication providers with payment processors through policy-enforced entitlements. Update reduces development time through pre-configured RLS (Row-Level Security) templates, automatic webhook synchronization between services, and real-time subscription status tracking that updates across both application logic and database permissions.

Main Features

1. Unified authentication system that extends existing providers (Supabase, Auth0) with billing-aware session management. The solution automatically syncs Stripe subscription status with user roles, enabling granular permissions through server-side policy files. Sessions include both authentication claims and commercial entitlements like active_plan or trial_end_date.

2. Subscription billing engine with pre-built components for pricing tables, checkout flows, and customer portals. The system handles prorated upgrades/downgrades between plans, implements metered usage billing through Stripe integration, and enforces subscription-based feature gating via API middleware. Revenue metrics and customer lifecycle events are exposed through a dashboard.

3. Extensible policy framework for multi-tenancy that connects authentication states with billing systems. Developers define organization structures (single-tenant or multi-tenant) through declarative YAML configurations, which automatically propagate to Supabase RLS policies and Stripe subscription hierarchies. The CLI tool generates type-safe client SDKs from these definitions.

Problems Solved

1. Eliminates manual synchronization between authentication systems and billing providers, which often causes security gaps when subscription status changes. Traditional implementations require separate coding for user roles, Stripe webhooks, and database permissions - Update automatically maintains consistency across all layers.

2. Targets full-stack developers building commercial SaaS applications who need to implement complex billing models (usage-based pricing, annual commitments) without becoming payment infrastructure experts. Ideal for startups and indie hackers using modern stacks like Next.js with Supabase.

3. Enables rapid deployment of scenarios like team-based subscriptions where billing status controls workspace access, or metered API platforms requiring real-time usage tracking. Supports compliance requirements through automatic audit logging of all entitlement changes across auth and billing systems.

Unique Advantages

1. Unlike standalone auth or billing services, Update provides orchestration between systems through its synchronization engine. Competitors require custom middleware development for equivalent functionality, while Update offers declarative configuration that generates both frontend components and backend validations.

2. Introduces policy-based entitlements that combine authentication claims with commercial status from Stripe. This allows feature gating through code-level permissions checks (update.auth.enforceSubscriptionActive()) while automatically maintaining corresponding database row security in Supabase.

3. Offers 10x faster integration than manual implementations through its create-update-app CLI that scaffolds complete auth+billing systems. The toolchain provides type-safe client SDKs generated from infrastructure configuration, eliminating API integration errors. Live reloading during development instantly propagates policy changes to both auth and billing providers.

Frequently Asked Questions (FAQ)

1. How does Update handle authentication provider compatibility? Update extends existing providers like Supabase Auth rather than replacing them, maintaining full compatibility with native SDK methods while adding billing context. Developers can still use standard signIn/signOut methods that now include automatic subscription checks.

2. Can I use custom Stripe subscription models with Update? Yes, Update's billing engine supports custom Stripe Products and Prices through its admin API. The system automatically syncs new plans to entitlement policies while maintaining existing subscription relationships through versioned schema migrations.

3. Does Update support multi-organization SaaS architectures? Update provides built-in multi-tenancy support through hierarchical policy definitions. Organizations can be configured as isolated tenants or collaborative spaces, with automatic propagation of membership changes to both Supabase RLS policies and Stripe subscription quantities.