Join other Sigilhosting users on Discord, follow our open-source work on GitHub, participate in forum discussions, and attend monthly office hours with our engineering team. Ask questions, share configurations, and contribute.
Real-time chat with other Sigilhosting users and our engineering team. Channels organized by topic: general discussion, technical help, feature requests, showcase (share what you've built), and off-topic. Our engineers participate actively — not community managers relaying questions to people who might answer them later.
The help channel is often faster than a support ticket for non-critical questions. Other users with similar setups can share solutions, and engineers can point you to documentation, known issues, or workarounds. For account-specific or security-sensitive issues, support tickets are still the right channel.
We don't moderate aggressively — the community is small enough that it self-regulates. We do enforce a code of conduct that boils down to: be respectful, stay on topic, and don't spam.
Our CLI tool, Python SDK, Go SDK, Node.js SDK, and Terraform provider are all open source under the Sigilhosting GitHub organization. Issues and pull requests are welcome on all repositories. Each repo has contributor guidelines, a code of conduct, and CI checks that run on PRs.
We also maintain community-contributed tools: example configurations for common architectures, deployment scripts, monitoring dashboards, and reference implementations for Sigilhosting API integrations. If you've built something useful with our infrastructure, we'd love to feature it in the community repositories.
Bug reports and feature requests filed as GitHub issues are triaged weekly by the engineering team. We label issues with priority and status so you can track progress.
For longer-form questions, tutorials, and discussions that benefit from threading and searchability, we run a discussion forum. Topics include deployment guides, architecture advice, performance optimization, and comparisons with other providers.
Forum threads are indexed by search engines, so they serve as a searchable knowledge base for common questions. When we see the same question asked multiple times, we create official documentation — the forum directly informs what we write in our docs.
Once a month, engineers host a live session on Discord where anyone can ask questions, request demos of features, discuss upcoming changes, or provide feedback on the platform. Sessions are recorded and posted to the blog.
Topics are collected in advance via a pinned thread in Discord, so engineers come prepared. Common themes include upcoming feature previews, deep dives into recent incident post-mortems, and live debugging sessions for tricky infrastructure problems.
Office hours also serve as a feedback loop — feature requests that come up repeatedly in office hours get prioritized on the roadmap.
Contributions aren't limited to code. Improving documentation, answering questions on Discord or the forum, writing tutorials, and sharing your deployment architectures all strengthen the community. We maintain a contributor recognition page that credits people for their contributions.
Discord, GitHub, forum, and monthly office hours.