Separate the public presence from the operational system.
CyberSaathi.in should remain a marketing/product website. Sensitive application services, APIs, data and administrative systems belong in separately secured environments.
Public Website
cybersaathi.in
Product information, capability pages, responsible-use information and demo requests.
Production API
api.cybersaathi.in
Dedicated production service endpoint with authentication, rate controls, logging and hardened deployment.
Application Portal
app.cybersaathi.in
Only if a web portal is introduced; not required for the existing Flutter apps.
Staging
staging.cybersaathi.in
Restricted pre-production environment with separate credentials and non-production data.
Development
dev.cybersaathi.in
Private/restricted environment. Avoid public exposure and never reuse production secrets.
Documentation
docs.cybersaathi.in
Can host controlled public or authenticated product documentation later.
Keep each deployable product independently maintainable.
Production principles
Separate secrets, databases and Firebase configurations by environment. Use HTTPS everywhere, restrictive CORS, secure headers, server-side validation, audit logging, least-privilege credentials, backups and a controlled release process. Exact controls should be validated against the final infrastructure before launch.
Public site at CyberSaathi.in. Operational code stays behind it.
This gives the brand a clean public presence without exposing application architecture or sensitive endpoints.