Continuous source-code access
Client-accessible repositories or mirrors keep work visible throughout the engagement. Production releases can be tagged, traced and transferred.
Trust. Continuity. Ownership.
Never locked to Etashi.
Useful technology should create leverage—not dependency.
Etashi is founder-led. We address that honestly by designing for client ownership, continuous source-code access, clear operational responsibility and a clean path to another competent provider if circumstances change.
01
Etashi principle
Your organisation retains the code, data, access and knowledge required to operate what we build.
No technical hostage situation. No proprietary mystery box around your own solution.
Client ownership
Source access that supports a real handover.
Sharing source code matters, but continuity requires more than periodically sending a ZIP file. The target is a reproducible, documented service that does not depend on one supplier’s laptop or memory.
Deployable
Build, configuration, database migration and rollback steps are documented.
Operable
Runbooks describe dependencies, monitoring, common failures and escalation.
Portable
Data export, deletion and third-party dependencies are made visible.
Replaceable
A competent provider can continue the service without Etashi-only assets.
Shared responsibility
Innovation and operational risk do not have to sit with the same supplier.
For enterprise work, Etashi can deliver the specialised application while the client and its incumbent managed-service provider retain production control, security monitoring, backup and disaster-recovery responsibilities.
| Responsibility | Client | Etashi | Managed-service partner |
|---|---|---|---|
| Business ownership, data classification and risk acceptance | Accountable | Consulted | Consulted |
| Application architecture, code, tests and technical documentation | Approves outcomes | Responsible | Supports integration |
| Cloud tenancy, identity, network and security monitoring | Accountable | Defines application needs | Responsible |
| Backup, restore and infrastructure disaster recovery | Accountable | Validates application recovery | Responsible |
| Application defects, behaviour and agreed enhancements | Prioritises | Responsible | Supports platform diagnosis |
| Supplier exit and replacement-provider appointment | Accountable | Provides handover | Supports transition |
The exact allocation is agreed per client, service and existing supplier contract.
Security & data integrity
Controls shaped around the service and the information it handles.
Access & secrets
Least privilege, MFA, controlled production access and secrets kept outside source code. Ownership and escalation are agreed before sensitive systems go live.
Data lifecycle
Authoritative sources, data minimisation, retention, deletion, subprocessors and data locations are made explicit rather than left to assumption.
RAG integrity
Source provenance, citations, versioning, permission-aware retrieval and predictable re-indexing help keep answers tied to approved business information.
AI-specific risk
Prompt injection, sensitive disclosure, excessive agency and model regressions are considered alongside conventional application security.
Founder-led, by design
Direct senior attention. Honest operational boundaries.
Etashi does not present itself as a 24×7 managed-service provider. We provide specialist application delivery and bounded support, then integrate with the client’s chosen operational and security partners where enterprise coverage is required.
AI helps accelerate research, implementation and testing. Human accountability, review and client ownership remain non-negotiable.
Start with the operating model