Skip to main content

What is the tech stack used for Fluxend?

We are using the following technologies to make Fluxend possible:Backend Stack:
  • Golang + Echo Framework — Primary language for API development
  • PostgreSQL — Robust database solution
  • PostgREST — Dynamic endpoints generated from database
  • Docker — Containerization for deployment
  • Goose — Database migrations management
  • Traefik — Automatically route traffic between containers
Frontend Stack:
  • Vite + React — Modern frontend framework
  • TailwindCSS — Utility-first CSS framework
No programming knowledge required! You don’t need to know Golang or React. You only need to have a basic understanding of how APIs work.With Fluxend, you can build whatever tables you want and use the auto-generated API for integration into your application — no coding required.
🏠 Hosted Version:
  • You host and maintain everything
  • 100% control over your infrastructure
  • Full responsibility for maintenance and updates
☁️ Cloud Version:
  • We maintain the database and infrastructure
  • You retain full control over your database
  • Export and migrate anytime you choose
  • Zero maintenance overhead
Currently in Early Alpha — We are in the early stages of development and wouldn’t recommend using Fluxend for production applications at the moment.This will change soon as we move toward stable releases. Stay tuned for production-ready versions!
Yes, absolutely! You can connect Fluxend with your existing PostgreSQL database using environment variables in the .env file.Database Configuration:
DATABASE_HOST=your-host
DATABASE_USER=your-username
DATABASE_PASSWORD=your-password
DATABASE_NAME=your-database
DATABASE_SSL_MODE=require
PostgREST Configuration:
POSTGREST_DB_HOST=your-host
POSTGREST_DB_USER=your-username
POSTGREST_DB_PASSWORD=your-password
POSTGREST_DEFAULT_SCHEMA=public
POSTGREST_DEFAULT_ROLE=your-role
Docker is required — Currently, there’s no way to run Fluxend without Docker. Docker ensures consistent deployment across different environments and simplifies the setup process.
We believe in transparency — We document features before implementation to give you visibility into our roadmap. Sometimes features are released in phases:
  • API endpoints might be available in earlier versions
  • UI/UX components may follow in later releases
  • Documentation clearly indicates when features are not yet available in the UI
This approach helps you understand what’s coming and plan accordingly.
We welcome contributions! Check out our Contribution Guide for detailed information on how to contribute to Fluxend, including:
  • Code contributions
  • Documentation improvements
  • Bug reports and feature requests
  • Community support
⌘I