🧱 Applications at Darukaa¶
Darukaa is composed of three primary applications, each serving a unique role in our ecosystem:
1. 🌐 Marketing Website¶
- Repo: Darukaa.earth
- Live URL: https://www.darukaa.earth
Description¶
This is the public-facing website that represents our brand and communicates our mission, features, and values. It is built for speed, accessibility, and SEO, and is usually updated by the marketing and design teams with support from engineering.
2. 💻 Web Application (Frontend)¶
- Repo: Product Frontend
- Staging: https://staging.darukaa.com
- Production: https://app.darukaa.com
Description¶
This is the core SaaS platform used by our clients. It provides tools for ESG data input, analytics, report generation, and overall sustainability tracking.
- Built with modern frontend frameworks (e.g., React/Next.js).
- Integrated with OpenAI for smart assistant features.
- Uses CI/CD pipelines on GCP for deployment based on merges to
main.
3. ⚙️ Backend API¶
- Repo: Product Backend
- Staging API: https://api.staging.darukaa.com
- Production API: https://api.darukaa.com
Description¶
Handles authentication, authorization, data storage, ESG scoring logic, AI processing, and integrations. This is the backbone of the platform that supports both internal and external clients.
- Deployed to GCP using automated Cloud Build pipelines.
- Single-tenant model for now (per client deployment not yet enabled).
- Communicates securely with the frontend and external data sources.
🚀 CI/CD & Hosting Overview¶
- All apps (frontend, backend, and website) are deployed via Google Cloud Platform (GCP).
- Cloud Build triggers on each repo watch for merges to
mainand automatically deploy to the appropriate environment (staging or production). - Static assets for the marketing site are hosted using GCP buckets or Netlify.
- Backend APIs are hosted on GCP Cloud Run.
- Frontend apps are served from App Engine or Firebase Hosting (depending on scale).
🧠 Note on Architecture¶
- We currently run a single-tenant SaaS model.
- Database is shared across tenants but access is scoped tightly per client.
- We plan to evolve to a multi-tenant architecture as we scale.