Core Panel Support Scope and Response Expectations
Contact [email protected] for product questions and technical assistance. Use the security reporting instructions for suspected vulnerabilities.
Prepare a useful support request
Include the installed Core Panel version, operating system and architecture, affected workflow, error text, approximate event time and timezone, and steps to reproduce. Describe the impact and whether the issue occurs in an isolated test environment.
Share redacted diagnostics only. Do not send root passwords, private keys, database URLs, recovery keys, or customer backups through ordinary messages or screenshots. Arrange an appropriate transfer method if sensitive evidence is needed.
Response times and availability
A measured average response time, fixed support hours, and a contractual response-time SLA are not published here. Ask the team to confirm availability and the response target for your request or service agreement. A response target is separate from a resolution deadline.
For paid professional services, scope, required access, delivery milestones, and dates are agreed in writing before work begins. Do not assume an ordinary product inquiry includes continuous monitoring or emergency server administration.
Product and customer responsibilities
Core Panel supplies server-management software. Infrastructure, third-party integrations, application code, dependency compatibility, and recovery planning remain workload-specific. Discuss migration, onboarding, and custom integration work separately so responsibilities and exclusions are clear.
The product security policy currently limits supported use to isolated development environments. Review that status before planning a deployment.
Subscription delivery problems
The service-delivery policy asks customers to contact support if access is not activated within one business day of confirmed payment. This activation escalation point is not a general technical-support response guarantee. Include the payment reference and account email.