Library / SDK
arrow-kt/arrow avatar
arrow-kt/arrow

Arrow for Kotlin: typed functional programming without leaving the language

The perfect companion for your Kotlin journey - Inspired by functional, data-oriented and concurrent programming

6,589 stars475 forksKotlinNOASSERTION

At a glance

What is it?
Arrow is a Kotlin library that supplies Option, Either, optics and typed error handling. It suits teams already on Kotlin who want functional data types and explicit failure paths, and it is a poor fit for anyone expecting a general-purpose framework.
Who is it for?
Adopt Arrow if your codebase is Kotlin and you want Option, Either and typed errors expressed in the type system rather than through exceptions. Do not adopt it as an application framework or as a substitute for coroutines, and do not expect the README to tell you how to roll back a release, because it does not.
Can I use it commercially?
Check first. The repository uses a licence we do not classify automatically, so read its LICENSE file before any commercial use.
Is it still maintained?
Yes. The repository received new commits within the last day.
What is it written in?
Mainly Kotlin, according to GitHub's language statistics.

Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.

From daily snapshots

Star history

  • arrow-kt/arrow6,589 ★ · +5
Star history
Repository2026-09-232026-11-15
arrow-kt/arrow6.6k6.6k

5 Stars in the last 53 days, measured from the daily GitHub snapshot. Compare with other projects

Editorial analysis

What Arrow adds to a Kotlin codebase

Kotlin ships nullability in the type system but leaves error handling to exceptions and sealed classes you write yourself. Arrow fills that gap with data types such as Option and Either, functional operators such as zipOrAccumulate, and computation blocks. The README describes the project as a library for Typed Functional Programming in Kotlin and states that it aims to provide a lingua franca of interfaces and abstractions across Kotlin libraries. That framing matters: Arrow is not a web framework, an ORM or a dependency injection container. It is a set of abstractions that other libraries can build on. The audience is Kotlin developers who already accept that a function returning Either<Error, Value> is more informative than one that throws, and who want that style supported by library code rather than by convention.

How the abstractions are organised in arrow-libs

The repository root holds build.gradle.kts, settings.gradle.kts, buildSrc/ and a single source directory, arrow-libs/. Everything published lives under that directory, which is why the README links to a Maven Central search for the group io.arrow-kt. The documentation is not in this repository. The README states plainly that the documentation is hosted in a separate repository, arrow-kt/arrow-website, and it lists the learning paths that live there: quickstart and setup, typed errors, coroutines and resources, resilience, immutable data, and collections and functions. That split has a practical consequence. If you find a gap in the API reference, the fix belongs in a different repository from the code you are reading. The build itself is Gradle, with gradlew and gradlew.bat at the root, a gradle/ wrapper directory, and a generator-scripts/ directory alongside buildSrc/, which suggests parts of the codebase are produced rather than written by hand. The presence of kotlin-js-store/ and a test-optics-gradle-plugin.sh script indicates the project is built for more than one Kotlin target.

Where to get Arrow and what the first step looks like

The README does not contain installation steps. It points to the quickstart and setup page on arrow-kt.io and shows a Maven Central badge linking to a search for the io.arrow-kt group. Those are the only coordinates the repository itself gives you, so confirm the version on Maven Central rather than copying one from a blog post. The README also names the types and operators the library provides, including Option, Either and zipOrAccumulate, and it links typed errors as a separate learning path, which is where the Either examples live. Because the README carries a Kotlin badge linking to the Kotlin 1.8 release notes, check it against your own compiler before you add the dependency.

Where Arrow stops being the right tool

Arrow does not replace coroutines, and the README treats them as separate concerns: the documentation lists coroutines and resources as its own learning path rather than folding it into the core types. If your problem is scheduling, cancellation or structured concurrency, the Kotlin standard library is the answer and Arrow is not. The second limitation is the licence metadata. The README's License section states the Apache License, Version 2.0, and the README carries an Apache 2.0 badge, but the repository metadata reports the licence as NOASSERTION. That mismatch means automated licence scanners may flag the project even though the file itself is unambiguous. If your organisation gates dependencies on scanner output, resolve that before you add the dependency, not after. The third limitation is release cadence. The most recent releases listed are 2.3.0-alpha.8 (2026-10-23), 2.3.0 (2026-10-26) and 2.3.0.1 (2026-10-27), so a stable 2.3.0 line now exists alongside the alpha builds. The last push to the repository was on 2026-11-01, so the project is not dormant.

Arrow compared with hand-rolled sealed classes

The realistic alternative is not another library. It is writing your own sealed class hierarchy for results and your own extension functions for mapping and flat-mapping over it. That approach has real advantages: no dependency, no version skew against your Kotlin compiler, and full control over the shape of the API. What it does not give you is the shared vocabulary. The README's stated goal is a lingua franca of interfaces and abstractions across Kotlin libraries, and that is the actual difference. A hand-rolled Result type is understood by your team and nobody else. Either and Option are understood by anyone who has used Arrow, and third-party libraries can target those interfaces directly. The cost of the shared vocabulary is that you inherit the library's release cycle and its abstractions, including the ones you do not need. A small service with one failure mode does not benefit from a typeclass hierarchy, and adding Arrow there is overhead with no payoff.

Maintenance, upgrades and licence implications

The repository is not archived and the last push was on 2026-11-01. Commits are landing. The release list shows 2.3.0-alpha.8 on 2026-10-23 followed by the stable 2.3.0 on 2026-10-26 and 2.3.0.1 on 2026-10-27. The README directs contributors to CONTRIBUTING.md and points users at Twitter, the Kotlin Slack channels and Gitter for questions, which means upgrade guidance lives in the documentation repository rather than here. The README does not document rollback, and it does not describe a deprecation policy for the types it exposes. On licensing, the LICENSE file and the README badge both point to Apache License 2.0, while the repository metadata reports NOASSERTION. Apache 2.0 is a permissive licence with an explicit patent grant, but this is a description of what the files say, not legal advice. If your organisation has a licence review process, feed it the LICENSE file and the badge rather than the metadata field.

Editorial conclusion

Adopt Arrow if your codebase is Kotlin and you want Option, Either and typed errors expressed in the type system rather than through exceptions. Do not adopt it as an application framework or as a substitute for coroutines, and do not expect the README to tell you how to roll back a release, because it does not. Before committing, check the Maven Central coordinates for the module you need and confirm that the Kotlin version badge in the README matches your project's compiler, since the README's Kotlin badge links to the Kotlin 1.8 release notes.

Frequently asked questions

What is the Arrow Kotlin library?

It is a library for typed functional programming in Kotlin. The README states that it provides data types such as Option and Either, operators such as zipOrAccumulate, and computation blocks, with the aim of offering a shared set of interfaces and abstractions across Kotlin libraries.

How do I set up Arrow in a Kotlin project?

The README does not list installation steps; it links to the quickstart and setup page at arrow-kt.io and shows a Maven Central badge linking to a search for the io.arrow-kt group. The version and the exact dependency snippet come from that page, not from the README.

Does Arrow replace Kotlin coroutines?

No. The documentation treats coroutines and resources as a separate learning path from the core data types, and the README lists them as distinct topics. Arrow covers types and abstractions such as Either and Option, not scheduling or structured concurrency.

Is Arrow actively maintained?

The repository is not archived and the last push was on 2026-11-01. The most recent releases listed are 2.3.0-alpha.8, 2.3.0 and 2.3.0.1 from October 2026, including the stable 2.3.0.

What licence does Arrow use?

The LICENSE file contains the Apache License, Version 2.0 and the README carries an Apache 2.0 badge, but the repository metadata reports the licence as NOASSERTION. That discrepancy is worth resolving with your own licence review before adopting it.

Official sources

  1. arrow-kt/arrow on GitHub
  2. Issues
  3. Project website
  4. README
  5. Releases
Add this badge to your README

If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.

Add this badge to your README

markdown
[![Hysen Labs](https://hysenlabs.com/badge/arrow-kt-arrow.svg)](https://hysenlabs.com/projects/arrow-kt-arrow)

Star history chart for your README

markdown
[![Star history](https://hysenlabs.com/chart/arrow-kt-arrow.svg)](https://hysenlabs.com/projects/arrow-kt-arrow)

Was this useful?