Why BYOL in Weblet?
Traditional platforms enforce bundled vendors for authentication, analytics, or billing—often resulting in higher costs, lock-in, and limited compliance flexibility. Weblet intentionally avoids this.
BYOL in Weblet enables:
- Tenant-level freedom to choose best-fit tools
- Direct ownership of licenses and data
- Reduced platform pricing and hidden markups
- Faster onboarding for enterprises already standardized on vendors
- Seamless migration between providers without platform refactoring
BYOL Architecture Principles
Weblet’s BYOL model is built on four core architectural principles:
- Adapter Pattern – Every external service integrates via a standardized adapter interface
- Tenant Isolation – Configuration, credentials, and data are scoped per tenant
- Graceful Fallbacks – Each module has a platform-safe default mode
- Non-Blocking Operations – Failure of an external service never breaks core user journeys
Authentication (BYOL)
Weblet supports external identity providers while maintaining a platform-level identity fallback.
Supported BYOL Scenarios
Tenants may integrate providers such as:
- Auth0
- Firebase Authentication
- AWS Cognito
- Enterprise SSO (SAML / OIDC)
How It Works
- Tenant configures provider credentials in Weblet
- Weblet routes authentication via the configured adapter
- User identity is normalized into Weblet’s internal user model
Fallback Strategy
If authentication is not configured or temporarily unavailable:
- Weblet activates native email-based authentication
- Magic links or OTP-based login can be enforced
- Access policies degrade gracefully (read-only, public, or limited scopes)
Subscriptions & Billing (BYOL)
Weblet separates access control from billing execution.
Supported BYOL Models
Tenants may use:
- Stripe
- Razorpay
- Chargebee
- External CRMs or ERPs for invoicing
Weblet’s Role
- Weblet does not charge end users on behalf of tenants
- It listens to subscription events (webhooks, APIs, sync jobs)
- Converts them into entitlements and access rules
Fallback Strategy
If no billing system is connected:
- Subscriptions can be tracked internally
- Access can be manually approved or time-bound
- Default plans (Free / Trial / Invite-only) remain operational
Analytics & Event Tracking (BYOL)
Weblet provides a unified Analytics Adapter Layer to log events across providers.
Supported Analytics Providers
- Google Analytics
- Plausible
- Mixpanel
- PostHog
Event Abstraction
Weblet tracks:
- Page views
- Content access
- CTA clicks
- Subscription actions
- Workflow transitions
Each event is normalized and forwarded to configured providers.
Fallback Strategy
If analytics is not configured or disabled:
- Events are logged internally (minimal, privacy-safe)
- No third-party scripts are injected
- Performance and UX remain unaffected
Other Integration Services (BYOL)
Weblet’s BYOL philosophy extends to all external dependencies:
Email & Messaging
- SMTP, SendGrid, ConvertKit
- WhatsApp providers (official APIs, BSPs)
Fallback: Internal queue + manual export
Search & Indexing
- Algolia, OpenSearch, Meilisearch
Fallback: Database-level search
Payments, CRM, Automation
- Tenant-selected vendors only
Fallback: Manual workflows or internal state tracking
Tenant Control & Governance
Each tenant:
- Owns all API keys and credentials
- Can rotate or revoke access at any time
- Can switch vendors without code changes
- Controls data residency and compliance posture
Weblet never resells licenses, never embeds tenant keys globally, and never assumes ownership of third-party data.
