Bu sayfanın Türkçesi var. Türkçe sayfaya geç
On-premise LMS

A corporate LMS that runs on your own server.

Saga is a learning management system installed on the organization's own infrastructure. The application and its database run together on the organization's server, sign-in goes through its directory, and mail leaves through its own mail server. There is no cloud service alongside it to buy or to operate.

InstallationOrganization's server
Application and databaseSame server, as containers Running
Active DirectoryUsers created at first sign-in Connected
Organization's SMTP serverOne-time codes and notifications Connected
Deployment model

The application and its database install together.

Saga is distributed as containers and runs on a server the organization owns or leases. Installation is a matter of completing the organization's settings and running a single command. The database ships with the application, and there is no separate component to license.

The model carries one requirement: the organization provides the server and maintains it. If that capacity is not available in house, we say so plainly during evaluation.

deployment
# complete the settings for your organization
cp .env.example .env

# install the application and its database
docker compose up -d
Existing systems

It connects to the systems the organization already runs.

Saga brings no new user directory, no new mail infrastructure, and no separate set of passwords. It uses what is already there.

Directory. Sign-in goes through Active Directory or LDAP. A user signing in for the first time is created automatically with a configured default role, and access ends when that account is disabled.

Mail. One-time codes and notifications are sent from the organization's own SMTP server, and every message is logged.

Bulk import. Users outside the directory are added in bulk from a CSV file, and the user list exports the same way.

Language. The interface is available in Turkish, English, and seven further languages. Each user chooses their own, and the choice is kept in their profile.

Security

A security review's questions are answered by the build.

Every sign-in requires a one-time code that is hashed, single-use, and time-limited, and no setting switches that step off for convenience. Stored SMTP and LDAP credentials are encrypted with AES-256-GCM. Each request carries a nonce-based content security policy and CSRF validation, and sign-in attempts are rate-limited per IP address and per account.

The container runs as a non-root user. Every release is scanned for dependency vulnerabilities and produces a CycloneDX software bill of materials. Accessibility is verified to WCAG 2.2 AA on every release by an automated gate.

Contact

Evaluate Saga on your own infrastructure.

Tell us about your server estate, your directory service, and your number of users. We will settle the installation requirements alongside the demonstration.

Request a demo