Know what is ready before you share the app.
Use this page as a calm checkpoint before giving PropertySync3 to trusted testers. It separates what is ready for private beta from what still needs attention before public launch.
Technical checks are passing
API environment: Production. Readiness profile: enterprise_saas. This supports the next controlled release step.
- Private beta can use controlled test data and a small trusted group.
- Public launch needs hosted email, backups, monitoring and reviewed legal wording.
- Tenant and contractor data must stay inside the landlord's organisation.
- Demo-only tools must not be exposed when real users are onboarded.
Private Beta V1 is about proving the repair journey.
The app should be tested with one landlord, a small property set, invited tenants, approved contractors and simple repair records.
Core landlord workflow
- Create a landlord account and start a 30-day trial.
- Add properties, tenants and approved contractors.
- Track one repair from report to contractor completion.
- Approve and close the repair with a saved repair file.
- Use property files and property documents separately.
Operational setup
- Host the web app and API on a stable private link.
- Use a real email or message delivery route for access codes.
- Confirm backup and restore for the production database.
- Prepare a simple support process for stuck testers.
- Review privacy, retention and terms wording before live data.
Do not treat beta as finished SaaS
- Do not invite unknown public users yet.
- Do not take payments until billing and plan enforcement are production-ready.
- Do not rely on local demo shortcuts for real tenants or contractors.
- Do not promise legal compliance until policies are reviewed properly.
- Do not store sensitive documents until hosting, backups and retention are proven.
Simple release stages
This keeps the next move clear. The goal is not to add more features too early; it is to prove the repair flow with real feedback.
Private beta
Small trusted group, controlled data, clear early-access wording.
- One landlord can complete the first repair journey without help.
- Tenant access and job-specific contractor links are understandable.
- Feedback can be captured from inside the real app flow.
- Hosting, database and email delivery are stable enough for testers.
- Privacy wording tells testers not to enter sensitive live data yet.
Paid early access
Limited paying users, real accounts, supportable onboarding.
- Production database, backups and restore process are proven.
- Email verification, password reset and invite delivery are live.
- Pricing and plan limits match what users see on screen.
- Support and admin review process exists for stuck users.
- Terms, privacy and retention wording are reviewed for UK/EU use.
Public SaaS launch
Wider market release with stronger operations and compliance evidence.
- Monitoring, alerting and error tracking are active.
- Security baseline, dependency checks and backup checks run regularly.
- Data retention and deletion workflows are operational.
- Billing, invoices and subscription state are automated.
- Incident response and customer support process are documented.
Technical checks from the API
These checks do not certify SOC 2, GDPR or ISO 27001 compliance. They show whether the minimum production guardrails are present.
Database connection succeeded.
Production database provider is PostgreSQL.
Core tenant-scoped entities include OrganisationId.
SMTP email delivery is configured.
Persistent outbound notification retries are enabled.
Private Azure Blob file storage is configured.
Expired security and delivery records are cleaned automatically.
Data-protection keys path is configured.
Development code exposure setting is safe.
AllowedHosts configuration is acceptable.
Demo mode setting is safe for this environment.
No obvious placeholder secrets were found in production settings.
Server-owned security audit event model is configured.
Application monitoring connection string is configured.
Security, deployment and SaaS readiness documents are present.
Data-retention policy is documented.