Welcome to Cloudberrie
Welcome to the Cloudberrie Manual—the single source of truth for how we build, operate, deploy, and maintain our products and services.
Whether you are joining the engineering team, working on a client project, or managing operations, this manual provides the standards, processes, and documentation needed to work consistently across Cloudberrie.
Purpose of this Manual
The Cloudberrie Manual exists to:
- Standardize engineering and operational practices
- Document business and technical decisions
- Reduce onboarding time for new team members
- Ensure consistency across products and projects
- Preserve institutional knowledge
What You'll Find Here
The manual is organized into the following areas:
| Section | Purpose |
|---|---|
| Getting Started | Onboarding and development setup |
| Company | Organization, domains, and business standards |
| Engineering | Development standards, Git, GitHub, releases |
| Infrastructure | Cloudflare, Firebase, hosting, DNS |
| Security | MFA, credentials, backups, access |
| Operations | Workspace, email, client operations |
| Products | Product documentation and architecture |
| Runbooks | Step-by-step operational procedures |
| Standards | Technical and operational standards |
| Decisions | Architecture Decision Records (ADRs) |
Development Philosophy
Cloudberrie follows a few core principles:
- Documentation first
- Automate repetitive work
- Build reusable systems
- Keep deployments predictable
- Prefer simplicity over unnecessary complexity
Where to Start
If you're new to Cloudberrie, read these documents in order:
- First Day Setup
- Development Workflow
- Repository Guide
- Engineering Handbook
Continuous Improvement
The manual is a living document.
Every significant engineering, infrastructure, or operational decision should eventually be documented here.
If documentation is missing or outdated, update it as part of your work.
One place for everything.
If it matters to Cloudberrie, it belongs in the manual.