Capabilities
Not a service list —a map of capabilities.
Every discipline is paired with the system that proves it. Design and marketing are still part of what we do — but at the centre is software that carries an institution's operation.
Multi-tenant architecture, database-per-tenant, domain resolution, provisioning automation and operator consoles.
What we build
- Multi-tenant architecture
- Database per tenant
- Custom domain management
- Operator console
Applications that turn an organisation's own processes into state machines, workflows and reports.
What we build
- State machines
- Approval workflows
- Roles and permissions
- PDF and Excel reports
Seen inDernek Yönetim Sistemi Bir Finans
LMS, live lessons, attendance, exams, coaching, practice-exam analytics and verifiable certificates.
What we build
- LMS and curricula
- Live lessons and attendance
- Exams and grading
- Verifiable certificates
Seen inNovademi PDR Platform
Association and professional-body infrastructure, from application and board decision to dues and ID cards.
What we build
- Applications and board approval
- Dues and collection
- Member ID cards
- Governance
Editorial workflow, blind review, DOI queues, indexing formats and scholarly metadata.
What we build
- Editorial workflow
- Blind peer review
- DOI and indexing formats
- Journal websites
Seen inNova JournalPort
Congress registration, abstract and review processes, program scheduling, badges and digital tickets.
What we build
- Registration and fees
- Abstracts and review
- Program scheduling
- Badges and certificates
Seen inNova CongressPort Novademi
Virtual POS, instalments, refunds, campaign engines, shipping integrations and e-Archive invoicing.
What we build
- Virtual POS and instalments
- Orders and refunds
- Shipping integration
- e-Archive invoicing
Seen inPDR Platform Novademi
e-Devlet and bank services, video-conference sync, job queues, scheduled jobs and data migration.
What we build
- e-Devlet and bank services
- Video-conference sync
- Queues and scheduled jobs
- Data migration
The public face of systems: interface design, theme systems, accessibility and search visibility.
What we build
- Interface design
- Theme systems
- Accessibility
- SEO and performance
Platform engineering
Multi-tenant architecture, database-per-tenant, domain resolution, provisioning automation and operator consoles.
What we build
- Multi-tenant architecture
- Database per tenant
- Custom domain management
- Operator console
Brand and communication
We build the platform, then make it visible.
We started as an agency, and creative and communication work is still on our desk: the team that builds the system tells the brand’s story with the same care.
Talk to us about brand and communicationCorporate identity
Logo, identity system and brand guidelines.
Brand consulting
Positioning, messaging and brand strategy.
Social media management
Content planning, design and account management.
Advertising and campaigns
Google and Meta ads, campaign management.
Corporate websites
An institution's public face: design, content, launch.
Digital transformation
Process analysis and an automation roadmap.
Engineering principles
Every principle isa practice you can see in code.
- 01
Rules live in code
The states an article, membership or order can pass through are defined in the model. Blind review, reversal-only corrections and payment gates are not left to user vigilance.
State machines · 5 systems
- 02
Consistency first
Payments and notifications are written to an outbox in the same transaction; orders carry idempotency keys; queue jobs are leased so none runs twice.
Novademi · PDR · Bir Finans
- 03
Secure by default
TOTP for admins, role and permission catalogues, CSRF and rate limits, file types verified by content, signed expiring file links, audit logs.
All Node systems
- 04
Isolation is architecture
In multi-tenant systems every tenant runs in its own database; separation is enforced by the data layer, not by query filters.
JournalPort · CongressPort
- 05
Nothing ships untested
Our systems carry more than 700 automated test files; money, permission and workflow rules are locked down by tests.
Unit, API and end-to-end tests
- 06
We operate what we build
Systems run on a container cluster we operate ourselves, with health endpoints, uptime monitoring and tagged image releases.
Containers · monitoring · CI/CD
Method
Problem → System → Architecture → Capabilities → Impact
- 01
Problem
We read the operation where it happens: who decides what, with which data.
- 02
System
We translate processes into states, roles and rules.
- 03
Architecture
We draw data boundaries, integrations and the scaling path up front.
- 04
Capabilities
We build module by module, with tests and against real data.
- 05
Impact
We launch the system, operate it and grow it with the operation.
Technology
Layer by layer, a real inventory.
Frontend
Server-rendered, separate admin apps
- Next.jsPDR · Novademi · JournalPort · Bir Finans
- ReactPDR · Novademi · JournalPort · Bir Finans
- TypeScriptPDR · Novademi · JournalPort · Bir Finans
- Filament · LivewireCongressPort
- BladeCongressPort · Dernek
Backend
Modular monoliths, dedicated background processes
- Node.js · ExpressPDR · Novademi · JournalPort
- NestJSBir Finans
- LaravelCongressPort · Dernek
Data
Database-per-tenant, job queues
- MySQLPDR · Novademi · JournalPort · CongressPort · Dernek
- PostgreSQLBir Finans
Infrastructure
A server cluster we operate ourselves
- DockerPDR · JournalPort · CongressPort · Novademi · Bir Finans
- CI/CDPDR · JournalPort · Dernek
The next system