Skip to content
⁨NDDev Dev⁩, home page
Community
Language: English
Display
Theme
Motion

Internal system and staff portal development

NDDev builds internal systems and portals: staff workspaces, directories, requests, a knowledge base and department workspaces behind a single sign-in. For the Almaty City Library Service we built the staff web interface, backend services and the integration with the library system: six months of development and support, and 50,000 users instead of the planned 2,000.

Who it is for

Organisations where staff juggle many separate programs and spreadsheets: public institutions, branch networks, service and manufacturing companies.

  • Single sign-in for staff
  • Directories and a knowledge base
  • Requests between departments
  • Integration with source systems

What an internal system is made of

An internal system gathers in one place what staff look for every day: a colleague directory, a knowledge base, news, IT and HR requests and their department’s work queues. There is one sign-in, through your company SSO on Keycloak, and each person sees what their role allows.

  • a staff portal with single sign-in through SSO
  • a staff directory and knowledge base
  • IT, HR and facilities requests
  • department workspaces with task queues
  • integrations with accounting and industry systems
  • roles, permissions and an activity log
  • observability and personal data removal in logs

The hardest part of internal systems lives in the integrations. At the Almaty City Library Service the backend of FastAPI services exchanges data with the library system through dedicated workers. We hold to one rule: the sync records an unknown value as a gap, and a member of staff fixes it. When the external system is down, the main path for readers and administrators keeps working.

For operations we separate environments: live, development and a dedicated observability server. Personal data and credentials are stripped from logs before they reach storage, and each environment has its own identity, so test and live data always stay apart.

How the system takes shape inside your company

Changes are checked in the development environment first and only then go to the live system.

  1. Survey

    We meet the departments and list the programs and spreadsheets they use and what should be brought together.

  2. Architecture and specification

    We design modules, roles, integrations and environments. For public bodies we write the specification to GOST 34.602.

  3. Modules one by one

    We launch the first module in the development environment and bring in users from one department.

  4. Integrations

    We connect the source systems and set up the sync and a gap list for staff.

  5. Live environment

    We move the system to the live server, connect monitoring and hand over an administrator guide.

Work in this area

  • Reading room of an Almaty public library, with wooden tables, teal chairs and bookshelves

    Libraries Almaty

    A mobile app for readers of the Almaty city libraries, a working interface for staff and a back end connected to the library's records system. Six months of development and support, and 50,000 users instead of the planned 2,000.

Questions about internal systems

How much does an internal system cost?

The price block shows the figure an internal system starts from. The total depends on the number of modules and departments, integrations with your programs, and security and documentation requirements. We fix the price and timeline of each stage in the specification.

Can the system run in our own infrastructure?

Yes. We deliver it in Docker and deploy it on your servers or in the cloud of your choice. Access, backups and monitoring stay under your control.

Do you work with public-sector organisations?

Yes. The Almaty City Library Service is one of our public-sector clients, and another project, in the customs field, is under NDA. For such projects we keep documentation to GOST 34.602 and work in agreed stages with fixed requirements.

How are the personal data of staff and citizens protected?

Role-based permissions, sign-in through SSO with two-factor protection, encryption in transit and an activity log. We strip personal data from logs and telemetry before it reaches storage, as we did for the Almaty City Library Service.

How long does development take?

The Almaty City Library Service project took six months of development and support. We give the timeline for your system after the survey and fix it in the specification by stage.

from $6,700

Free warranty
60 days

Prices are starting prices for information only and are not a public offer. The final price is fixed in the specification.

Digitalisation and business systems

List the programs your staff work in

Tell us which of them should be brought together and who uses them. We will suggest an architecture for the system.

We reply within 24 hours

Assistant

Loading the assistant…