Technical Architecture
A high-level view of how Harla is built — the stack, the infrastructure decisions, and the principles that govern them.
Architecture overview
Architecture diagram
Add a system architecture diagram here. It should show the main components — inbound channels, the AI pipeline, the data store, and the operator-facing interface — and how they connect. Draw it to the level a technical investor would expect, not a developer-facing spec.
Technology stack
Stack summary
List the key technology choices — frontend, backend, infrastructure, database, AI providers — with a one-line rationale for each. Focus on the decisions that are non-obvious or that reflect a considered trade-off.
Infrastructure and hosting
Infrastructure summary
Cloud provider, deployment model (serverless / containerised / VM), region (UK data residency is material for GDPR), backup and disaster recovery posture. Include current monthly infrastructure cost if available.
Security posture
Security summary
Authentication model, data encryption (at rest and in transit), access controls, and any third-party security tooling in place. Note if penetration testing has been conducted or is planned.
Scalability considerations
The current architecture is designed for the pre-seed period — fast to build, fast to change, and sufficient for the first cohort of pilots. Deliberate decisions have been made to avoid premature scaling infrastructure that would slow development without delivering customer value at this stage.
[Add specific notes on what would need to change to go from 10 to 100 to 1,000 concurrent customers, and at what point those investments become necessary. Be honest about the current constraints — sophisticated investors respect engineers who know what they have deferred and why.]