Answers for technical buyers and partners.
Use this page to understand the platform boundary, partner model, public code strategy, and operational assumptions before starting a deployment.
What is MNSCloud?
MNSCloud is a modular API-driven platform for telecom, hosting, monitoring, cyber security, support, CRM, and infrastructure automation.
Can a partner use this website under their own domain?
Yes. The website is static-first, CMS-managed, and can be built for another domain by changing site settings and deployment configuration. The public content remains focused on MNSCloud unless a partner customizes it.
Does the agent require inbound ports?
The agent model is outbound: it connects from the server to the MNSCloud API to receive jobs and report status. This avoids opening management ports only for remote automation.
Can customers use both SIP and WebRTC extensions?
Yes. The proposed WebRTC edge model lets selected extensions register through WebRTC while the same tenant/domain model continues to protect multi-tenant SIP identity.
Why are some repositories public?
Public repositories make clients, installers, agents, website code, and edge connectors auditable and easier to improve. The private API/control plane remains responsible for authority, policy, billing, routing ownership, and secrets.
Can external developers contribute?
Yes. Contributions go through Pull Requests, CI, security review, and maintainer approval. MNSCloud may sponsor, contract, or hire contributors by explicit written agreement.
Is this website legal advice?
No. Trust, privacy, cookie, and legal templates provide a professional structure, but production legal text must be reviewed for the target jurisdictions.
Build on a platform designed for operators.
Talk to MNSCloud about deployments, integrations, public connectors, and enterprise security requirements.