Current beta promise
During beta preparation, Prepost should be honest about what is ready and what is still gated.
The public site can collect beta interest, show the workflow, provide free tools, and explain the roadmap. It should not claim production publishing, billing, or real OAuth readiness until those gates are passed.
Required gates
Before real OAuth, real publisher adapters, callbacks, webhooks, billing, or public launch claims, these areas must be ready:
- staging and production deployment paths;
- release and rollback process;
- smoke checks for staging and production;
- Stripe configuration and webhook handling;
- social app credentials and callback URLs;
- platform-specific error handling;
- support path for failed connections and failed posts.
What users can do before full launch
Beta users can:
- join the beta list;
- review the product workflow;
- use the free tools;
- read setup and limitation docs;
- prepare their account access before connection is enabled.
What Prepost should not promise yet
Before the gates are complete, avoid promising:
- live OAuth for every user;
- automatic production publishing to every platform;
- payment-card checkout;
- trial billing;
- fixed response-time support SLA;
- platform support beyond the stated MVP scope.