Enterprise Control Center
Scalability, compliance, security and operations at a glance.
This system does not assume that a research-only label makes a product lawful to sell, distribute, import, export or market. Every product and jurisdiction requires appropriate legal/regulatory review before commercial distribution. Products that may be considered unapproved drugs or otherwise regulated products are especially flagged and must not be published without review.
Capacity Report
- Base44 plan limits: NO PUBLISHED HARD MAXIMUM IDENTIFIED for distributor or user accounts on the current plan. Verify current plan quotas in the Base44 dashboard (billing/usage) before large-scale recruitment.
- Storage, credits and integration usage: REQUIRES VERIFICATION — visible in your Base44 dashboard usage/credits views; not exposed to the app itself.
- Architecture: Distributor accounts are isolated by roles and row-level security with no per-distributor schema, so the same architecture scales from 100 to 10,000+ distributor accounts without structural change. List queries are bounded (≤500 per view) and paginated.
- Recommended upgrade threshold: No numeric threshold can be honestly stated without published limits. Monitor dashboard usage metrics and page response times; load-test progressively at 100 / 500 / 1,000 / 5,000 / 10,000 users before each scale milestone.
System Health
RLS + roles + private documents active. Security testing still required before launch.
0 open reviews · 0 countries pending legal review
No processor connected. Written processor approval of the business model is required before activation.
Manual fulfillment workflow active. Carrier APIs not connected.
Public assistant live — restricted to approved catalog data only.
Managed by Base44 — usage metrics visible in the platform dashboard.
Architecture ready for 10,000+ accounts; load testing not yet performed.
0 recent admin actions recorded.
Security Readiness
Base44 does not make the application immune to hackers — the two columns below separate platform-provided security from PeptLife configuration.
Base44-Provided Security
Provided and enforced by the platform for all app traffic.
Platform-managed accounts, sessions, password reset and verification.
Managed by Base44 infrastructure — plan-specific details REQUIRE VERIFICATION.
Platform-managed tokens and sessions.
Server-side secrets only; never exposed in public JavaScript.
Platform-managed. No specific recovery time/point can be claimed without verification — REQUIRES VERIFICATION.
Platform-level protections exist but are not publicly specified — REQUIRES VERIFICATION.
PeptLife Global Configuration
Orders, shipments, applications, commissions, payouts and documents are owner- or admin-scoped.
Admin / user roles with admin-only management surfaces.
Distributor documents live in private storage; signed access only after ownership/admin check.
The assistant receives only published, review-approved product data. No accounts, orders, payments or private documents.
Distributor approvals, shipment overrides and compliance changes are recorded with before/after values.
Platform auth MFA options — enforce at the account level; status REQUIRES VERIFICATION.
NOT ACTIVATED. A payment processor must first confirm in writing that this business model, products and jurisdictions are permitted before activation.
Not connected. Carrier selection is pluggable — connect after carrier selection and credential review.
Run the Base44 security scan and a full review before launch — NOT YET PERFORMED.
Progressive load testing plan required before large-scale deployment — NOT YET PERFORMED.