Nova CongressPort
Everything a congress secretariat does, in one system.


Screenshots from the live system's public pages.
01 — Problem
Congress secretariats juggle a separate website, registration forms, payment tracking, abstract and peer-review processes run over email, and badges, certificates and invitation letters made by hand. Every year the same chaos is rebuilt.
02 — System
We built a multi-tenant platform that gives each congress its own domain, database and theme. Attendee accounts, registration and fees, abstracts, reviewer assignment, the scientific program, documents and publication run as one flow; an operator CRM manages tenant provisioning, licences and domains.
Abstract review
Assignment, conflicts of interest and reviewer load are computed by the system.
- 01Submission
- 02Auto-assignment
- 03Blind review
- 04Decision
- 05Acceptance letter
- 06Program & book
Revision → back to author
Nova CongressPort — kongre yönetimi
Submission
Auto-assignment
Blind review
Decision
Acceptance letter
Program & book
03 — Architecture
The central app resolves the tenant from the domain and binds the request to that congress's database. The operator CRM provisions, suspends and re-domains tenants through a signed internal lifecycle API.
- L0Users
- Attendees
- Authors
- Reviewers
- 7 admin roles
- L1Interfaces
- Congress site · TR/EN
- Member panel
- Admin panel
- Operator CRM
- L2Application
- Laravel 11
- Filament 3
- Livewire 3
- Signed internal API
- L3Modules
- Registration & fees
- Abstracts
- Review assignment
- Program
- Documents
- Publication
- Live sessions
- L4Data
- Central MySQL
- Database per congress
- MinIO (S3)
- L5External services
- PayTR
- Zoom
- Google Meet
- Google OAuth
- Resend
- Netgsm · Mutlucell · Twilio
04 — Capabilities
- 01
Registration and pricing
Fees by participation type, gala and capacity-limited workshop add-ons, discount codes, title and association-member discounts, and KVKK consents logged with IP and device.
- 02
Payments and reconciliation
PayTR iframe payments with hash-verified callbacks; receipt upload and admin approval for bank transfers; email/SMS payment reminders and a multi-sheet finance export.
- 03
Abstracts and peer review
Abstracts with up to 10 authors, oral/poster/online formats; single or double-blind review, automatic assignment with load balancing and conflict-of-interest checks; reviewers fenced to their own inbox.
- 04
Scientific program
Halls, session types and panels; room and speaker conflict detection, an automatic scheduler, PDF/CSV export and a per-session .ics calendar file.
- 05
Documents
Badges, invitation letters, attendance and author certificates, workshop certificates, acceptance letters; visual layout editors, bulk PDF and payment-gated access.
- 06
Publication and archive
Abstract book and full-paper book PDFs, ZIP archive; multi-year congresses per tenant and a past-congresses page.
- 07
Site and content
6 themes, editable homepage sections, menus, pages, blog, key dates and committees; Turkish and English content fields.
- 08
Operator layer
A CRM for tenant provisioning, suspension, domain management, licence windows, template deployment and audit logging.
05 — Impact
- 01
A congress's site, registration, collections, abstracts and documents are run from one panel.
- 02
Registration, abstract, gala and workshop intake can be opened or closed without a deploy.
- 03
A congress clones its structure into next year; previous years remain in the archive.
- 1:1
- database per congress
- 2
- blind review modes
- 6
- congress site themes
- 7
- admin roles
- 6
- document types generated
- 5
- SMS provider options
Technology stack
Frontend
- Blade
- Livewire 3
- Filament 3
Backend
- PHP 8.4
- Laravel 11
- stancl/tenancy
Data
- MySQL
- MinIO (S3)
Documents
- dompdf
- TCPDF
- FPDI
- OpenSpout
Infrastructure
- Docker Swarm
- Portainer
- nginx
- supervisord

