Architecture

System context for Solar Sanchalak on Aegis SaaS.

This page shows the operational and system context behind Solar Sanchalak: who uses it, what external systems support it, and why a managed cloud foundation matters for secure, traceable workflow execution.

System Context

A high-level view of users, platform boundary, and external systems.

The public architecture view is intentionally high level. It shows the real actors and supporting systems without exposing internal implementation details or sensitive interfaces.

System context diagram

System context diagram for Solar Sanchalak showing field technician, solar EPC operations team, customer site supervisor, the Solar Sanchalak SaaS platform, Firebase Authentication, communication providers, and Google Cloud.

Aegis Solar Sanchalak is a multi-tenant SaaS platform for solar EPC companies to digitize AMC service operations end to end. It connects field technicians, operations teams, and customer supervisors through structured evidence capture, approval workflows, and signed digital service reports. Built on Google Cloud, it helps solar service businesses improve transparency, reduce disputes, and scale maintenance operations with confidence.

Operational users

The diagram shows real field, operations, and customer-side roles rather than an abstract software concept.

Clear platform boundary

Solar Sanchalak sits inside a defined system boundary with explicit dependencies around identity, communications, and cloud.

Cloud with purpose

Managed cloud is tied directly to evidence handling, authentication, approvals, notifications, and reliable service delivery.

Actors

The platform coordinates real field work, review, and approval.

Solar Sanchalak is built around operational roles that already exist in solar AMC: field execution, internal review, and customer-side approval.

Field technicians

Capture site evidence, complete assigned visits, and submit structured records from the field.

EPC operations team

Plans service work, reviews field execution, and manages customer-ready reporting and follow-up.

Customer supervisors

Review service proof, validate the visit outcome, and approve completed work with stronger confidence.

Managed Cloud

Why a managed cloud foundation matters for this product.

This is not infrastructure for its own sake. Managed cloud services matter here because evidence, approvals, identity, and retrieval all require reliable system behavior across multiple sites and users.

Identity and controlled access

Users need structured authentication and role-aware access across technician, operations, and customer-facing workflows.

Evidence and reporting

Photos, signatures, readings, and generated reports need secure storage, retrieval, and durable linkage to workflow state.

Reliable operations

Delivery depends on hosted APIs, notifications, background processing, observability, and consistent deployment discipline.

Support Use

How startup credits and infrastructure support can accelerate delivery.

For credit-review or investor conversations, the important point is not abstract scale. It is that cloud resources directly support product execution, evidence handling, user access, and the next layer of AI-assisted data processing.

Current technical needs

  • Application hosting and backend APIs
  • Authentication and access workflows
  • Evidence storage and report generation
  • Notifications and customer approval links

Next infrastructure layers

  • AI-assisted extraction from images and readings
  • Validation and structuring of operational data
  • Scalable retrieval and reporting
  • Observability, resilience, and controlled growth

Architecture Value

Architecture built for operational credibility and managed-cloud scale.

This system context is meant to show that Solar Sanchalak is being built as a serious operational platform: grounded in real user workflows, supported by clear system dependencies, and aligned with the kind of managed cloud foundation that startup-credit programs and infrastructure reviewers expect to see.