Services and data with you
Application services, the dashboard, and operational data run in your company infrastructure.
MassAccess On-premise
MassAccess in your infrastructure
A business communication platform on your own servers. Send messages to customers through Telegram and MAX bots, and receive replies and new inquiries in your system.
Kubernetes with external data storesYour infrastructure provides data-store high availability
Customer communication under your control
For companies that need to host services and operational data in their own infrastructure and control their upgrade schedule. Your technical team will handle installation and maintenance.
Changes on your schedule
Your team chooses when to upgrade, using documented verification and rollback procedures.
Send and receive messages
MassAccess sends messages to customers through company bots and passes replies and new inquiries to your system.
What stays with you and what remains in the cloud
With MassAccess on-premise, application services and operational data run in your company infrastructure. Licensing and usage accounting remain in MassAccess cloud services. External connectivity is required.
In company infrastructure
- Platform, dashboard, and API
- Bot settings, workflows, and operational data
- Monitoring, backups, and upgrades managed by your team
In MassAccess cloud services
- License issuance and status
- Signed usage metering
- Tariff, balance, and updates
External connectivity is required
A fully isolated installation is not supported. The server or cluster needs outbound access for licensing, metering, images, and messenger integrations.
Deploy MassAccess on a server or in Kubernetes
Install MassAccess on a company server or in your Kubernetes cluster. Each option has its own requirements and installation guide.
Docker Compose
For a company hosting the platform on its own Linux server. The package includes the required services and installation scripts.
Open the Compose installationKubernetes and Helm
For a company with an existing Kubernetes cluster. Helm delivery fits established operational processes.
Open the Kubernetes guideWho maintains MassAccess in your infrastructure
On-premise gives your team control of hosting and the ongoing responsibility to operate it.
Your team
- Provides a server or cluster, network, and secure access
- Monitors services, data, and backups
- Plans and runs upgrades
MassAccess
- Provides the deployment package and installation guides
- Issues the license and meters platform usage
- Delivers application updates
How on-premise is billed
There is no separate fee for the deployment package. Outbound messages follow your company tariff: available bonus messages are used first, then your account balance.
View pricingOutbound message priceRUB 0.59
How to connect MassAccess in your infrastructure
Start in your account. Your IT team can handle the installation method and technical requirements.
Register your company
01Create a MassAccess account and open the on-premise section in your dashboard.
Choose your deployment
02Select Docker Compose or Kubernetes and review the requirements for your infrastructure.
Install and verify
03Get the package and license, follow the guide, and test your first customer communication flow.
Questions about MassAccess deployment
Key deployment conditions to review with your technical team.
How does on-premise differ from the MassAccess cloud version?
In the cloud version, MassAccess hosts and maintains the platform application. With on-premise, services and operational data run in your company infrastructure; your team handles installation, upgrades and backups. Licensing and usage accounting remain in MassAccess cloud services, so both options require external connectivity.
Can we use the platform without internet access?
No. Licensing, message metering, image delivery, and messenger integrations require documented outbound access.
Which data stays in our infrastructure?
Application services, the dashboard, API, settings, and operational data run in your environment. Cloud services receive license status and signed usage data; delivery involves the selected messenger.
Who handles maintenance and backups?
Your team operates the server or cluster, monitors services, handles backups and recovery, and schedules upgrades. MassAccess provides the package, updates, and documentation.
Is there a separate fee for the deployment package?
No. The package has no separate fee. Outbound messages follow your company tariff; bonus messages are used first if assigned at registration.
Should we use a server or Kubernetes?
Docker Compose fits a company-managed Linux server; Kubernetes and Helm fit an existing cluster. Compare each method’s requirements with your team’s capabilities.
Run MassAccess in your environment
Register your company, choose a deployment method, and connect customer communications to your systems.