How we choose technology

This is an important topic with more to come, but it must be addressed because developers often become very territorial over their tech stack.

Inevitably, some people will be offended by the choices in the Aven tech stack. This is ok, as long as we have a values-driven methodology of choosing technology, and a mechanism for evolution when we hear community feedback.

  • We choose technology that meets our values
  • Coming soon: Link to new tech evolution page

App Framework Dependencies

The Aven Cloud framework and the Sky site depend on:

  • NodeJS 12 or 14
  • TypeScript
  • React
  • Next
  • Next-MDX-Enhanced
  • Emotion
  • Express
  • Docker
  • PostgreSQL
  • Prisma 2
  • Debian
    • Nginx
      • LetsEncrypt
  • GitHub
    • Actions

We use a variety of other small dependencies in Aven Sky, including: jwt-simple, fs-extra, cookie-parser, body-parser, bcrypt, pojo-maps, @expo/spawn-async, remark plugins: autolink-headings, slug

Indirect Dependencies

  • Webpack (through Nextjs)

Cloud Manager Dependencies

Service Providers

To deploy and run our app, we require a variety of services. Eventually the Aven Stack will be agnostic to all service providers, but Aven currently integrates with:

  • GitHub (repo, actions)
  • Digital Ocean (DNS, VPS, S3, Postgres)
  • SendGrid (email)
  • Stripe (recurring billing)

In the operation of Aven Sky we also use the following:

  • CloudFlare (CDN, maybe)
  • Gandi (Domain registrar)

Additional Relevant Technologies

  • HTML
  • CSS
  • HTTP
  • CDN
  • Email
  • Fonts

© Aven LLC. Open Source under Apache 2.0