I’m stuck on agent installation. Where should I ask?
Use Documentation for the baseline flow first. If you believe you hit a product bug, open a GitHub issue with OS version, agent build, and a minimal reproduction narrative—without posting secrets.
A practical hub—not a promise of every social network
We prioritize channels we can staff and archive: source hosting, first-party documentation, and product pages you can link to from tickets. That keeps answers discoverable for the next engineer—not buried in a closed chat scrollback.
If you are evaluating Certinite for production, start with Documentation and Security, then open a workspace when you are ready to run a proof of concept on a non-production host.
Where to engage today
Use the right channel for the job: reproducible bugs and feature ideas belong in GitHub; conceptual questions and architecture are best anchored to documentation links.
GitHub
Review public material, open issues, and follow repository activity. This is the best place for reproducible bug reports and engineering-facing feature discussion tied to code or release artifacts.
Visit GitHub →Documentation
Start here for control plane vs. agent responsibilities, issuance flows, and operational language that matches how the product is built.
Open documentation →Blog & announcements
Product news, launch notes, and longer-form context when we ship meaningful platform changes.
Read the blog →Features overview
A structured capability index optimized for scanning—helpful before you ask “does Certinite support X?” in a thread.
Browse features →Community guidelines
Short rules that protect both operators and end users:
- Do not post private keys, PFX passwords, activation secrets, or customer tenant identifiers in public threads.
- Redact hostnames and IP addresses when they are not essential to reproduce an issue.
- Prefer logs and versions (agent build, OS, web server stack) over screenshots alone.
- Assume readers are operating production systems—mark destructive steps clearly and avoid “try this blindly” advice without rollback context.
- Commercial procurement, BAAs, and custom security reviews should route through Enterprise contact paths—not ad-hoc public posts with sensitive legal detail.
Community FAQ
Can Certinite staff answer questions in GitHub?
We monitor public repositories for actionable issues. Response times vary; production-impacting incidents for paying customers should use the support channel associated with your agreement.
Do you run an official Discord or Slack?
This page lists the channels we maintain today. If we add real-time community spaces, we will publish them here and in announcements so links stay authoritative.
How do MSPs discuss multi-tenant workflows?
Read the MSPs page for positioning, then use Features and Documentation for shared vocabulary. Avoid sharing customer-identifying details in public forums.
Ready to try the product?
Create a workspace, install an agent on a lab host, and validate a full issuance cycle before fleet rollout.