eradiant docs

About ERADIANT

Welcome to ERADIANT – the platform for modern, data‑driven event and community formats.

ERADIANT is developed by ECENT and helps organisations plan, run and evaluate events, programmes and communities in a structured way.

What is ERADIANT?

ERADIANT is a modular, comprehensive event tool. Instead of running separate tools for ticketing, communication, programme planning and networking side by side, ERADIANT brings these functions together in a single integrated platform:

  • Contacts & organisations: Central data base for people, institutions and roles.
  • Events & modules: Reusable event structure with modules for tickets, programme, mailings, networking and voting.
  • Multi‑tenant capability: Multiple teams can work independently on the same ERADIANT instance.

Core modules

  • Contact module
    Manage contacts, leads and institutions in one place, including segmentation and history.
  • Event module
    Control all aspects of an event:
    • programme planning and schedules
    • event mailings
    • networking (1:1 meetings, locations, time slots, participant properties / filters)
  • Voting module
    Create votes and elections, define questions, options and target groups – integrated with your existing contact and event data.
  • Ticketing module
    Sell tickets via shops, manage orders and check‑ins, use payment providers (e.g. Stripe) and connect ticketing data to events (event synchronisation).
  • Organization module
    Manage members, roles and permissions, email sending configurations and payment providers at organisation level.

Who is ERADIANT for?

ERADIANT is designed especially for:

  • organisations with events of any size (programmes, festivals, conferences, demo days)
  • venues that want to structure their events and use a shared software platform
  • networks, associations and hubs that coordinate many stakeholders

The focus is on process reliability, data quality and good usability for organising teams and participants.

Technology & architecture (in short)

  • Frontend: Next.js (React) with modern App Router architecture.
  • Data storage: Supabase (PostgreSQL) as the central, strongly typed data source.
  • Multi‑tenant: Separation of organisations via organisation IDs and a carefully designed permissions model.

You can find more details on the technical architecture in the individual module and developer chapters of this documentation.

Next steps