OSS TanbouSign in with GitHub

use strongly typed SQL and sequence-style entity APIs on pure JDBC

About these scores

OSS scale score is an unbounded metric that log-compresses and weights Stars, Watchers, Forks, and Contributors. Discovery score is the current OSS scale score minus the score at discovery. Update pace is commits in the last 30 days, growth momentum is the OSS scale score difference within the recent observation window, and OSS health is a 0–100 rating based on available recency, Community Health, and release data.

Stars
2,345
Primary language
Kotlin
License
Apache-2.0
Repository last updated
Jun 20, 2026
On this page

Overview

Ktorm is a lightweight Kotlin ORM built directly on pure JDBC. It combines a strongly typed SQL DSL with entity sequence APIs, giving Kotlin applications detailed control over generated SQL while keeping queries idiomatic.

Features and best fit

Based on official documentation; not hands-on tested · Content checked:

Key features

Build queries with a strongly typed SQL DSL

Table schemas are represented as Kotlin objects and queries can express filters, joins, aggregation, unions, inserts, updates, and deletes through typed DSLs.

Sources: [1]

Use entity APIs modeled after Kotlin sequences

Entity sequence APIs provide operations such as filter, map, and sortedBy, mirroring familiar Kotlin collection and sequence patterns.

Sources: [1]

Best fit

Fits Kotlin/JVM backends that want ORM conveniences without hiding SQL

It works well when teams want entity mapping and query composition while retaining fine-grained control over generated SQL without mandatory XML or annotations.

Sources: [1]

Before adoption

Treat database access as blocking because the core is pure JDBC

The README describes Ktorm as built directly on JDBC. Coroutine-based applications should still isolate database calls appropriately and size connection pools for blocking I/O.

Sources: [1]

Version 4.2.1 fixes an NPE in the KSP Maven plugin

The v4.2.1 release specifically fixes an NPE in the KSP Maven plugin, which matters for builds using that integration.

Sources: [2]

Official sources

  1. [1]Ktorm README(2026-10-06)
  2. [2]Ktorm v4.2.1 release(2026-10-06)
Supplemental curator note

It fits Kotlin/JVM backends that want ORM conveniences while retaining fine-grained SQL control. It is built on JDBC rather than R2DBC, so plan for blocking I/O.

Try it in 3 steps

  1. 1

    Get the source

    git clone --depth 1 https://github.com/kotlin-orm/ktorm.git
  2. 2

    Enter the repository

    cd ktorm
  3. 3

    Check the official steps

    Continue with the commands in the README Installation, Quick Start, or Getting Started section.

    find . -maxdepth 1 -iname 'README*' -exec sed -n '1,220p' {} \; -quit
Check the official README

Growth

Growth trends · Last 30 days

2,345 Stars

Trend data is still being collected.

Development activity

Last 90 days · weekly

Commits (last 30 days)
0
Open PRs
7

Development activity is still being collected.

Built with

Categories and tags

GitHub data

GitHub dataView detailed GitHub data

GitHub Topics

  • kotlin
  • orm
  • sql
  • ktorm
Stars
2,345
Forks
160
Watchers
31
Open issues
96
Contributors
29
Owner type
Organization
Primary language
Kotlin
License
Apache-2.0
Repository last updated
Jun 20, 2026
Write a related article

Share a guide or use case for this OSS in Markdown. Articles are published after administrator approval.

Report incorrect information

Tell us if any listing information is incorrect or outdated.

After reading this page, do you know what to do next?