QCS Information Hub
A public reference for information, documentation, and active projects related to QCS infrastructure and development.
This site is a central reference for technical documentation, prototypes, and project updates. Everything published here is intended to be public.
What's New
- What's New — the latest release highlights, right on the home page.
- Roadmap — what's in progress, what's planned, and what has shipped.
- Articles — the latest QCS posts from Medium.
- FAQ — answers to common questions about this hub and QCS services.
- Engineering Notes — practical how-tos, written in Markdown, starting with building a static site with Hugo. Includes search, topic tags with their own pages, a table of contents, copy buttons on code, linkable headings, related notes, updated dates, and an RSS feed.
Upstream Services
Live status of the third-party platforms QCS projects depend on, grouped by what each one does and read from the provider's own status feed. This is not a status page for QCS services — it reports only on these upstream dependencies. Each bar is one day, built from incidents the provider reported, so it reflects disclosure rather than measured uptime.
-
Database Checking…90 days ago today
-
Source control & CI Checking…90 days ago today
-
CDN & DNS Checking…90 days ago today
-
Edge hosting Checking…90 days ago today
-
Application backend Checking…90 days ago today
Prototypes & Active Projects
Documentation and information about QCS projects.
- Infrastructure documentation
- API references
- Architecture guides
- Deployment procedures
Rizal Center
An interactive platform showcasing community and organizational information.
Visit Prototype →Roadmap
What QCS is working on, what is planned next, and what has recently shipped.
In progress
Rizal Center
Interactive platform for community and organizational information.
Planned
Search engine indexing
Register this site with Google Search Console and Bing Webmaster Tools and submit its sitemap.
Search-friendly note titles
Retitle engineering notes to match how people search, such as "How to Host a Hugo Site on Amazon S3".
Engineering notes on Medium
Cross-post engineering notes to Medium, credited to this site as the original source.
QCS service status
A status section for QCS's own services, alongside the upstream providers already tracked.
Expanded technical documentation
Architecture guides, API references, and deployment procedures for active projects.
Shipped
Information hub rebuild
This site, rebuilt as a Go static site with upstream status and policy pages.
Articles
Articles on QCS projects, infrastructure, and engineering will appear here as they are published. In the meantime, follow along on Medium.
Documentation
Technical documentation, guides, and reference materials for QCS development and infrastructure — architecture diagrams, setup instructions, and best practices.
Available Documents
Privacy Policy
Privacy policy and data handling practices for QCS services, including Garmin Health API compliance and user rights.
Read Policy →Security Policy
How to report a vulnerability privately, and what to expect after you do.
Read Policy →Accessibility
Our accessibility commitment, known limitations, and how to send feedback.
Read Statement →Engineering Notes
Practical how-tos on infrastructure, tooling, and development, learned hands-on.
Browse Engineering Notes →Contributing Guidelines
How to report issues, suggest improvements, and submit updates to this hub.
Read Guidelines →Looking for agreements?
Blank agreement templates and client policies are published on our main site. Executed, client-specific documents are never posted publicly — they're delivered to clients directly.
View agreement templates →Frequently Asked Questions
Is the status section a status page for QCS services?
No. It reports only on the third-party platforms QCS projects depend on, read from each provider's own status feed.
Where can I find QCS agreement templates and client policies?
Blank agreement templates and client policies are published on qcloud.systems. Executed, client-specific documents are never posted publicly.
How is wearable and health data handled?
See the Privacy Policy, including the section on Garmin Health API compliance.
How do I report a security vulnerability?
Please report it privately — not in a public issue. The Security Policy explains how.
How can I suggest a correction or improvement to this site?
Open an issue on GitHub, or see the Contributing Guidelines.
Contact & Collaboration
For questions or feedback about QCS projects, reach us on Medium or GitHub.
Contribute to This Hub
This information hub is maintained as an open project. We welcome contributions, feedback, and improvements from the community.
- Report Issues: Found an error or outdated information? Open an issue on our repository.
- Submit Updates: Have improvements to suggest? See our contributing guidelines for the submission process.
- Documentation: Help us improve technical documentation and guides.