Local conversations
Conversations, files, operators and settings stay in the installation database and storage.
Architecture without vague promises
Know where data lives and why each external service is used
EasyChat keeps valuable conversations on the installation server. External systems receive only data required by an explicitly enabled feature.
Free start: 300 delivered operator push targets. The web chat keeps working after the limit; FCM, WebPush and SMS become available with a license.
What you get
Minimal push signal
The central FCM gateway receives an event, installation and chat_id but does not store text or attachments.
Controlled integrations
AI and messenger APIs are used only after the installation owner configures them.
How it works
Verify HTTPS and PHP
Production needs valid TLS, PHP 7.4+, MySQL/MariaDB and current extensions.
Limit access
Use roles, unique passwords, Passkeys where available and protected backups.
Review external channels
Grant minimum API permissions and never expose tokens in logs or screenshots.
Self-hosted
What to know upfront
Conversations, files, users and settings stay on your server.
- Self-hosted does not mean zero external requests: push, AI and messengers call their APIs when enabled.
- Files are validated against allowed MIME types; documents are served as attachments with nosniff.
- Security also depends on hosting, PHP/CMS updates and the owner's backup policy.
Frequently asked questions
Does the central server store conversations?
No. The central gateway handles licenses and minimal push signals while conversations stay in the installation.
Can AI be disabled?
Yes. AI is not required for chat or channel operation.
Can we request a pre-deployment review?
Enterprise teams can request an architecture, integration and operational boundary review.
Next step
Request a reviewVerify EasyChat with your own workflow
Start free. Move to a license only after the widget, operator panel and phone work together in your environment.