A database/framework for defining, querying, and storing structured data efficiently across platforms. It supports powerful features like advanced querying with filters and aggregations, cross-platform serialization (JSON, YAML, ProtoBuf), and historical data versioning.
Surfaced from shared tags and platforms — no rankings paid for.
Maryk lets you define a strongly typed data model once, then use that same model for validation, serialization, querying, storage, tooling, and sync across Kotlin Multiplatform targets.
Use Maryk when you want:
Maryk is a good fit for local-first apps, cross-platform products, Kotlin-heavy backends, tools that need typed data files, and systems where schema evolution and incremental sync matter.
Start with the website for the best reading path. Source docs live in this repository and the website is maintained in website/.
Maryk is Kotlin Multiplatform. Platform support depends on the module:
rocksdb-multiplatform bindings.Add the core dependency:
repositories {
mavenCentral()
}
dependencies {
implementation("io.maryk:maryk-core:<maryk-version>")
}
Define a model:
import maryk.core.models.RootDataModel
import maryk.core.properties.definitions.date
import maryk.core.properties.definitions.string
import maryk.lib.time.LocalDate
Person : RootDataModel<Person>() {
firstName string(index = 1u)
lastName string(index = 2u)
dateOfBirth date(index = 3u)
}
johnSmith = Person.create {
firstName with
lastName with
dateOfBirth with LocalDate(, , )
}
Person.validate(johnSmith)
json = Person.Serializer.writeJson(johnSmith, pretty = )
fromJson = Person.Serializer.readJson(json)
For a complete model → store → query flow, read Getting Started or First Store Tutorial.
libfdb_c.See store/README.md for the decision guide.
Useful commands:
./gradlew jvmTest
./gradlew :store:memory:jvmTest
./gradlew :cli:jvmTest
cd website && yarn build
When editing website pages generated from repository docs, update the source file listed in website/README.md.
Issues, discussions, docs fixes, examples, store improvements, and PRs are welcome. Good first contributions usually live in docs, examples, tests, CLI/App workflows, or store-specific edge cases.
libfdb_c) is available.libfdb_c is available).