CMS · See how it works
From proposal to publication.
One governed conference system — every manuscript visible, every role scoped, every privileged action audited.

Lifecycle
Proposal to archive — one governed spine.
Every manuscript stays visible. Every privileged action stays audited. Step through the conference cycle the platform actually runs.
Proposal
Organisers submit a structured conference request — basics, tracks, deadlines, budget — into an approval queue.
- Multi-step conference request
- Super Admin approval queue
- Direct create with tracks when authorised
Stages — scroll sideways
Roles
Seven scoped operators.
Conference-scoped RBAC — a user can be Reviewer in one venue and Track Chair in another. Privileged scope re-resolves from the database on each request.
Researcher
Submit manuscripts, track review, manage revisions, pay fees, download certificates.
Scope
Own submissions only
Journey
Register or accept invite → profile → browse open calls → wizard → track status → revision → decision → pay → camera-ready → certificate.
Architecture
Portal · API · storage · optional ML.
- Architecture nodes
Focus
Portal
Next.js 15 · edge auth cookie · rate-limit · SEO
Capabilities
What the platform actually ships.
Submission
Six-step wizard with drafts, author lookup, PDF validation, and replace-after-submit.
Review
Double-blind modes, structured scoring, COI gating, bidding, and review history.
Payments
Registration fees with bKash / SSLCommerz, mark-paid flows, and reconciliation.
Certificates
Acceptance, presentation, publication, review, and meta-review certificates.
DOI & citation
Archival carries DOI/citation metadata with proceedings bundling.
Publication
Proceedings generation from the accepted set — publisher-ready close-out.
Email & Send Center
Transactional SMTP plus console broadcasts, templates, and communication logs.
Reports
Track and platform reports, reviewer workload views, and exports.
Analytics
Dashboards for chairs and admins — real aggregates only, never invented KPIs here.
AI assistance
Optional ML: similarity risk levels, track suggestion, and analytics sidecars.
Automation
Optional ML — assist, never invent proof.
Similarity, track suggestion, and analytics ride as a FastAPI sidecar. Core governance does not depend on them.
Similarity detection
Risk levels (Low / Medium / High) from the ML sidecar.
Track suggestion
Assist chairs when routing manuscripts to the right track.
Metadata validation
Server-side validation on every wizard step.
Reviewer assignment aids
Pool, invite, and bulk assign with COI checks.
Deadline extensions
Request, approve, reject, or modify extension days.
Notifications
Targeted in-app and email per user, role, and conference.
Security
Three enforcement layers. Full audit trail.
RBAC
Seven conference-scoped roles plus Platform Owner on cms-ops.
Three enforcement layers
Edge middleware · API JwtAuthGuard/RolesGuard · UI guards.
Audit logs
Privileged mutations recorded — roles, finance, decisions, system.
Session control
Rotating refresh tokens; privileged scope re-resolved from DB.
Transport & headers
Helmet, CSP posture, rate limiting, brute-force lockout.
Storage posture
Object storage for manuscripts — not serverless local disk.
Integrations
Wired for real conference ops.
- Google OAuthProduction redirect pinned; profile completion for first login.
- SMTP / Send CenterConsole credentials override env; sent/failed logged.
- bKashPayment integration via stored credentials.
- SSLCommerzPayment integration via stored credentials.
- Supabase Storagesubmissions + conference-assets buckets.
- ORCID-ready authorsAuthor records support scholarly identity fields.
From proposal to publication — everything in one governed system.
Request a demo with your real conference scenario, open the live portal, or read the product page.
