Can I run FastRestful entirely on my own infrastructure?
Yes. The backend is Django + DRF and the frontend builds as a self-contained Vite application. Production expects PostgreSQL, a shared Redis URL, HTTPS origins, and a valid Fernet encryption key. Object storage is optional but recommended for media.
How do paid platform plans get published?
Operators configure platform plans in Django admin with display amounts, provider price IDs, workspace limits, API listing limits, benefits, and a recommendation. A paid plan stays unpublished until at least one matching amount and recurring price ID pair is configured.
Are vendor API plans included?
Yes. Vendors create their own product plans with monthly or annual prices, quotas, overage, trials, coupons, and endpoint entitlements. That revenue flows through invoices and payouts; it is separate from platform subscription billing.
Which payment and payout providers are supported?
Checkout supports Stripe, PayPal, Flutterwave, Paystack, and Razorpay. Payouts support Stripe Connect and PayPal Payouts. Provider credentials can come from environment variables or admin-managed gateway records, with admin records overriding field by field.
Do I need Cloudflare or a specific frontend host?
No. The frontend can be served by any static host or Node-compatible runtime supported by its build. Cloudflare is supported for the product-host and edge deployment path, but not required. Keep API origins, CORS, CSRF trusted origins, and canonical URLs aligned.
What happens if I outgrow the default plan limits?
Platform subscription limits are enforced server-side but configurable by the operator. Vendors can manage API listing limits per plan, and the gateway enforces quotas and rate limits per subscription. Existing products are preserved across downgrades; new listings above the cap are blocked.