CND StudioCND Studio

Enterprise software and technology services

Software built around the way institutions work.

CND Studio develops systems that follow an institutional process from start to finish, and assesses and operates the infrastructure those systems depend on. Our platforms Nasirus and Congirus, for academic publishing and scientific event management, are used under licence by universities and other institutions.

Scope of work

Custom software

Project based
Tracking and automation systemsIntegration and service layersReplacement of end-of-life systemsDocument and report automation

Technology consulting

Defined scope and duration
Architecture assessmentInfrastructure and server operationSecurity review and incident responseAI integration

Platforms

Licensed use
Nasirus · publishing managementCongirus · scientific event management

What we do

Custom software, technology consulting and two platforms

Approval steps, permission schemes and form structures are kept as configuration rather than written into code. This allows the software to follow the institution when its organisation or procedures change. We apply this approach in our own platforms and in client projects alike.

Custom software

Systems designed around institutional processes

Software that follows a process from beginning to end, connects to existing systems through service interfaces and is designed for long-term operation. This includes integration layers, the replacement of end-of-life systems without data loss, and document and report automation.

Technology consulting

Assessment and direction for an existing system

Not every requirement calls for new software. We assess architecture, operate infrastructure and servers, review security and respond to incidents, and define the scope and data boundaries of AI integrations. The deliverable is a written, reasoned and prioritised report.

How it runs

How we work with an institution

  1. Discovery

    We document how the institution works today, down to who does what and how. At this stage the subject is the process, not the software.

  2. Scope and rollout decision

    Which modules to start with, and where the rollout ends, is decided together with the institution. Not everything has to be switched on from the first day.

  3. Configuration

    Forms, roles, approval steps and document templates are set up to match the institution’s own order of work. This is configuration, not a code change.

  4. Migration and go-live

    Existing records are transferred according to a plan, in stages rather than in a single cut-over.

  5. Support and release management

    After go-live, support, updates and the activation of further modules follow an agreed schedule.

Principles

What we consider essential in enterprise software

Decisions are made by people
The system prepares the acceptance letter; the editor makes the acceptance decision. It prepares the print job; the institution approves the print. Automation takes over the routine work around a decision, not the decision itself.
Every step is recorded
Who decided what, and when, is held in an audit trail that cannot be altered afterwards. The reasons for a decision remain traceable years later.
Ethical rules are enforced by the system
The separation of reviewer and author identities is applied by the system itself rather than left to the attention of individual users.
The institution chooses the deployment model
A hosted installation or one running on the institution’s own servers. Where the data is kept is the institution’s decision.

Security

Responsibility for institutional data

Both platforms rest on role-based access, permission-driven screens and an unalterable audit trail. Uploaded files are scanned for malware. Official documents carry a verification stamp, and their authenticity can be checked on a public verification page. This gives recipients an independent way to confirm an acceptance letter or certificate.

Personal data is processed under KVKK in Türkiye and the GDPR in Europe. With an on-premises installation, data remains within the institution’s own infrastructure.

Our approach to information security

Let us discuss your institution’s processes

A demo call follows your own workflow. Together we identify which module is the sensible starting point.