CepatEdge

Appearance

Handover and Positioning (Generic) ​

This document describes how to present and hand over the system to any institution or client. It is generic; it does not assume a specific organisation.

For university-specific handover (our strategy, checklist, files to remove/leave, and docs for the institution), see the isolated folder:

  • docs/university/ — All institution-specific handover material. That folder can be deleted when re-branching for another client.
  • docs/institutional-readiness/ — Institutional gap assessment and hardening plan (SSO, governance, DR, ownership) used when talking to risk-averse IT/security teams.

Generic Positioning ​

  • Present as: A cloud-native maintenance management system optimized for cost efficiency and audit transparency, and offer a demo.
  • Lead with: Workflow clarity, reduced manual overhead, role accountability, data ownership. Quiet confidence; no ego, no savior energy.
  • Avoid: Leading with “it’s free” (low perceived value), tech hype (DO, Workers), or overconfident security claims. Let impact and clarity speak first.

Design for Clarity ​

The system should be understandable by people who do not share our vision: e.g. tired sysadmin, cautious security officer, skeptical infra manager. Clarity is a requirement; vision alignment is a luxury. Hand over understanding, not just code.

Portability ​

  • API: Hono runs on Node and other runtimes.
  • Database: Standard PostgreSQL with Drizzle ORM (no vendor lock-in).
  • Storage: S3-compatible; can be swapped.
  • Caching: The edge-native part is Durable Objects. Moving off DO is a consistency-model replacement (e.g. Redis or similar), not a one-line swap — be ready to explain that to IT.

Security ​

Security is layered; we stay paranoid, not overconfident. See Security Overview. When presenting to an institution, emphasise audit transparency and accountability rather than absolute claims.

For institution-specific strategy (real win, if rejected, 12-month commitment, files to remove/leave), use docs/university/our-planning/ and docs/university/handover/.