Version History, Real Changes & Honest Release Notes

Highlights

Version 1.3.0 is the current foundational launch release for PanelConfig. The focus of this release is public product clarity, operator trust, documentation depth, and launch-readiness polish around the existing platform surfaces. It does not claim a backend rewrite; the purpose is to make the product easier to understand, review, install, and operate.

• Refreshed the public website content around PCAdmin, PCUser, PCCLI, API, installation, pricing, security, documentation, changelog, roadmap, and status.
• Expanded the documentation foundation so operators can understand hosting accounts, DNS, SSL, email, databases, backups, security, automation, and troubleshooting from a single documentation portal.
• Added API documentation groundwork based on the current read-oriented API resources and token model, with write workflow guidance clearly separated from available endpoints.
• Added PCCLI documentation groundwork around current commands, safe server-side automation, jobs, SSL issuance, backup jobs, health checks, and planned command coverage.

PCAdmin

PCAdmin remains the operator surface for provider-side work. The release improves the clarity of how providers should think about accounts, packages, domains, services, security records, audit logs, release readiness, and administrative workflows without changing existing route behavior.

• Clarified provider operations messaging around users, hosting accounts, packages, domains, DNS, websites, email, SSL, backups, services, logs, and security.
• Improved product copy for operator workflow pages so the interface feels less like a prototype and more like a maintained hosting platform.
• Preserved existing permissions, routes, forms, and app logic.

PCUser

PCUser messaging has been refined around real customer hosting work: domains, DNS, websites, email, databases, SSL, files, FTP, backups, cron, logs, and account visibility. This release keeps the customer panel direction focused on practical hosting tasks rather than abstract SaaS wording.

PCCLI

The documentation now explains PCCLI as a server-side operational surface for repeatable tasks, job execution, account review, service checks, backup jobs, SSL jobs, and release verification. Current commands are documented separately from planned command coverage.

API

The API documentation has been expanded around bearer token authentication, request logging, rate limiting, current read-oriented resources, and integration-ready direction. The documentation avoids presenting planned write endpoints as live.

Security

The public security position now explains accountable operations, CSRF-protected forms, prepared statements, session practices, rate-limited logins, audit records, token handling, command allowlists, file upload safety, and responsible disclosure. No external certifications or fake compliance claims are added.

Notes

Existing deployments can import the new content safely on staging first. The release keeps version 1.3.0 as the latest public version and preserves the homepage changelog behavior that reads the newest published changelog entry.

Highlights

Version 1.2.0 expanded the security and operational record foundation used by PanelConfig. The work centered on giving providers better visibility into security events, service records, SSL orders, file operations, job activity, and account-level operational history.

Security

• Expanded security-center direction around security events, IP blocks, firewall records, WAF rules, malware scan records, login history, and audit review.
• Kept security language grounded in what the platform stores and displays, avoiding certification or compliance claims that have not been completed.
• Improved guidance for operators reviewing suspicious access, repeated failed logins, and risky configuration changes.

SSL and Jobs

SSL work was aligned with job-style operations so certificate requests and renewals can be treated as operational tasks that produce records instead of invisible background changes. This improves troubleshooting when DNS validation, ACME communication, or service reload steps need review.

Files and Service Records

File operation records and service inventory records were clarified as operational evidence. They help providers answer practical questions: who changed a file, what service was reviewed, whether a task was queued, and which area needs attention.

Fixes and Polish

• Refined Security Center wording for provider operators.
• Improved SSL pipeline descriptions and troubleshooting language.
• Aligned release notes with the actual product surfaces visible in the application and public website.

Highlights

Version 1.1.0 focused on making the two main panel surfaces clearer for their intended users. PCAdmin is for providers and operators. PCUser is for customer hosting work. The release improved the language, navigation expectations, and visible workflow structure around both surfaces.

PCAdmin

• Clarified PCAdmin as the operator home for users, packages, hosting accounts, domains, services, security controls, logs, and audits.
• Improved dashboard messaging so provider teams can understand which modules are operational, customer-facing, or security-sensitive.
• Preserved existing permission boundaries and route structure.

PCUser

• Refined the customer dashboard direction around websites, domains, DNS, email, databases, SSL, FTP, files, backups, and support.
• Clarified that customer views should show enough operational detail for self-service without exposing provider-only controls.

Documentation

Initial documentation planning was aligned with how hosting providers actually operate: account lifecycle, DNS and SSL dependency, email authentication, backup safety, resource usage, support visibility, and audit history.

Highlights

Version 1.0.2 tightened the installation and release-readiness story. The installer direction now emphasizes fresh-server preparation, hostname and DNS review, firewall awareness, installer lock safety, and post-install checks.

Installer

• Clarified that installer lock files exist to prevent accidental reinstallation over an existing deployment.
• Improved operator guidance for fresh server preparation and post-install review.
• Kept installer documentation separate from application feature claims so providers can see what setup work is required before production use.

Release Audit

Release audit records were treated as an important internal practice for verifying packaging, schema readiness, routes, public pages, and operational files before publishing a release package.

Fixes

• Improved release note clarity around installer safety.
• Refined readiness wording for operators preparing staging and production installs.

Highlights

Version 1.0.1 cleaned up public-facing pages around pricing, billing expectations, contact, legal content, and product positioning. The goal was to make PanelConfig easier for providers and reviewers to understand before installing or purchasing.

Public Website

• Improved wording around pricing plans and expected hosting-provider use cases.
• Refined footer links, product navigation, and company-page messaging.
• Updated public content to keep PanelConfig positioned as a hosting control panel platform rather than a generic SaaS template.

Legal and Trust Pages

Privacy Policy, Terms of Service, About, Contact, Security, Roadmap, Changelog, and Status pages were aligned with PanelConfig, LLC language. The content avoids fake certification claims and keeps responsibility boundaries clear for self-hosted deployments.

Highlights

Version 1.0.0 established the core PanelConfig foundation: public website, authentication, PCAdmin, PCUser, PCCLI, API resources, installer records, content records, and readiness tooling. This release is the base that later documentation, security, automation, and integration work builds on.

Core Platform

• Introduced PCAdmin as the provider/operator side.
• Introduced PCUser as the customer hosting panel.
• Introduced PCCLI as a server-side command interface for operational tasks and automation.
• Introduced API v1 resources with token-based access and request records.
• Established the public pages needed for product explanation, install guidance, docs, changelog, roadmap, status, security, pricing, and contact.

Operational Foundation

The release focuses on the records a hosting platform needs: users, accounts, packages, domains, DNS, websites, email, databases, SSL, backups, cron, services, security events, logs, jobs, API tokens, and audit history. Some areas are already surfaced through UI/API/CLI, while deeper workflow automation remains planned in later versions.

PanelConfig now includes API token management, API v1 endpoints, PCCLI foundation, installer records, server health visibility, content records, and release audit tooling

PanelConfig now includes the first connected account, plan, PCAdmin, and PCUser foundation screens used by the provider workflow

The official website direction now centers PanelConfig as a serious hosting control panel platform with PCAdmin, PCUser, PCCLI, integrations, installer, API, and security messaging

Highlights

Version 0.9.0 was a foundation preview used to align the project around a real hosting-provider workflow. It helped define the separation between public website, PCAdmin, PCUser, PCCLI, API, installer, database records, and product documentation.

Direction

• Separated provider operations from customer hosting tasks.
• Defined the role of audit records, job records, service records, and security records in the product direction.
• Established the naming and positioning for PanelConfig, PCAdmin, PCUser, PCCLI, and API.

Note

This release is included for historical clarity. It should be treated as a foundation milestone rather than a production feature-complete release.