Technology Choices
Teams may choose their own stack.
Requirements
- All software must be source controlled via repositories hosted on HCI’s GitHub account.
- Applications should be hosted on HCI’s Coolify infrastructure
- If your software relies on other SaaS services to function, those services must be evaluated and managed by HCI Technology Department
Recommendations
- Use one language across the stack. Pick a complementary stack, so that one language covers the frontend, backend and tooling. This reduces how many languages a team has to know and HCI has to maintain.
- Prefer mainstream, well-supported tools. Widely used frameworks with active maintenance are easier to hand over, hire for and patch.
- Automate code style and static checks. Use strict type checking, a linter and an automatic formatter. Commit their configuration to the repository and run them on every pull request, so style is settled by tools and not by review comments.
- Follow the platform's guide. Projects built on Hope.Cloud follow the Hope.Cloud developer guide for project structure, linting and conventions.
- Do not handle payments yourself. Use an established payment provider, so card details never touch HCI systems.
- Manage your reliance on AI. AI pricing, terms and availability can change, and a single provider can become a lock-in. Software should keep working, and people should still be able to maintain it, if an AI tool or model is withdrawn or becomes too expensive. Keep AI features and AI-assisted workflows portable between providers. HCI's self-hosted models are one alternative.
Preferences
These are the default choices at HCI where several good options exist. A project can choose differently and notes what it chose.
- Language and stack: TypeScript across the stack, with React and Next.js.
- Payments: Stripe, or 7me.
- Dependency scanning: GitHub security scanning, Snyk or Socket.
- Diagrams: draw.io, Excalidraw, Mermaid or Archify.