Changelog

Product evolution, visible and reviewable.

MNSCloud uses public repositories, documented patterns, and release notes so partners can understand how the ecosystem is evolving.

Website trust and proof surfaces

  • Added architecture, company, use case, status, changelog, and FAQ pages.
  • Expanded the website CMS so marketing and partner teams can edit public proof content.
  • Added responsive coverage for the new public pages.

Public website foundation

  • Created the static MNSCloud website with Astro.
  • Added Decap CMS for git-based content editing.
  • Added blog, legal pages, cookie consent, developer repositories, and domain boundary validation.

Security and public repository strategy

  • Documented public client boundaries for agents and service connectors.
  • Established contribution governance, repository files, and CI expectations.
  • Defined service-based Cyber Security profiles around CrowdSec and nftables.

Infrastructure connector direction

  • Separated agent, Asterisk, FreeSWITCH, Kamailio, OpenSIPS, and WebRTC edge work into standalone public repository models.
  • Defined outbound agent behavior and API-driven execution patterns.
  • Expanded hosting provider direction for VPS, containers, storage, and future provider APIs.