
Typed plugin API enabling runtime‑independent HTTP applications; agnostic core and HTTP layers with adapters to bridge applications to host runtimes, simplifying deployment across diverse environments.
Koyane (こやね, pronounced "koh-yah-neh") is a Kotlin framework with a typed plugin API. Applications use common Kotlin, with Kotlin/JS and Kotlin/Wasm adapters for Fetch hosts, Node.js servers, and HTTP functions. Core and HTTP are runtime-independent; adapters connect applications to host runtimes.
The API is experimental.
All adapters target Kotlin/JS and Kotlin/Wasm. Choose your hosting service, then add the module listed below. Application code uses the same runtime-independent Core and HTTP APIs on every host.
| Service | Runtime used by Koyane | Module | Example |
|---|---|---|---|
|
|
Cloudflare Workers runtime | koyane-cloudflare-workers |
Cloudflare Workers |
|
|
Node.js | koyane-lambda |
Lambda HTTP events |
|
|
Node.js | koyane-node |
Lambda HTTP server |
|
|
Node.js | koyane-node |
Cloud Run functions |
|
|
Node.js | koyane-fetch |
Vercel |
|
|
Supabase Edge Runtime (Deno) | koyane-fetch |
Supabase |
The runtime column identifies the runtime used by this implementation; services may offer other runtimes. Kotlin/Wasm runs through a JavaScript entry point within that runtime. Lambda Event Functions support API Gateway HTTP API and Function URL payload 2.0. Cloud Run functions use Google's Node.js Functions Framework. Compatibility is checked locally; deployment to these cloud services is not verified.
The following hosts can run the Node.js HTTP server on either Kotlin target. On virtual machines such as Compute Engine, run directly on Node.js or use a container. Container services run the same application packaged as a container image.
| Service | Runtime used by Koyane | Module | Deployment |
|---|---|---|---|
|
|
Node.js | koyane-node |
Directly or in a container |
|
|
Node.js | koyane-node |
Directly or in a container |
|
|
Node.js | koyane-node |
Directly or in a container |
|
|
Node.js | koyane-node |
Directly or in a container |
|
|
Node.js | koyane-node |
Directly or in a container, such as Docker |
|
|
Node.js | koyane-node |
Container |
|
|
Node.js | koyane-node |
Container |
|
|
Node.js | koyane-node |
Container |
|
|
Node.js | koyane-node |
Container |
|
|
Node.js | koyane-node |
Container |
|
|
Node.js | koyane-node |
Container |
|
|
Node.js | koyane-node |
Container |
|
|
Node.js | koyane-node |
Container |
|
|
Node.js | koyane-node |
Container |
|
|
Node.js | koyane-node |
Container |
|
|
Node.js | koyane-node |
Container |
|
|
Node.js | koyane-node |
Container |
|
|
Node.js | koyane-node |
Container; existing App Runner customers only |
These are hosting options for the Node.js server; service-specific deployment configurations are not included.
Icon sources: Diagrams, SVG Logos, Vercel, and Lucide via Iconify.
dev.quwac.koyane:koyane-bom aligns the versions of all Koyane library modules.
Import the BOM and add the modules used by your application without individual versions.
The BOM does not add libraries or install plugins automatically.
These snapshot coordinates require local Maven publication.
For a released version, use mavenCentral() and that release's BOM version.
The snippet below belongs in a Kotlin Multiplatform build targeting js, wasmJs, or both.
repositories {
mavenLocal()
mavenCentral()
}
kotlin {
sourceSets {
commonMain.dependencies {
implementation(project.dependencies.platform("dev.quwac.koyane:koyane-bom:0.0.1-SNAPSHOT"))
implementation("dev.quwac.koyane:koyane-cloudflare-workers") // Choose the module for your service above.
// implementation("dev.quwac.koyane:koyane-logging")
}
}
}All adapters expose HTTP and Core transitively.
For a runtime-independent library, use dev.quwac.koyane:koyane-http with the same BOM.
Source-based multi-project builds can use implementation(project(":koyane-http")) directly.
Install HTTP explicitly and return an HttpResponse from every handler.
import dev.quwac.koyane.core.koyane
import dev.quwac.koyane.http.Http
val app = koyane {
install(Http) {
get("/hello/:name") { text("Hello, ${param.string("name")}!") }
}
}Optional modules provide content negotiation, explicit JSON codecs, CORS, Bearer authentication, error handling, logging, date/time inputs, and in-memory application tests. See the cheat sheet for API examples and behavior.
Core and HTTP are independent of Fetch and host bindings. CloudEvents, SQS events, API Gateway payload 1.0, and ALB events are outside the HTTP adapters' scope.
The adapters have no database or driver dependency; applications supply their own database clients. Applications that need database access are expected to use Kagiroi as their database client. The current HTTP model uses buffered text bodies. Binary or streaming bodies, automatic request binding, OpenAPI generation, client generation, and a JVM server adapter are not part of this repository.
Koyane (こやね, pronounced "koh-yah-neh") is a Kotlin framework with a typed plugin API. Applications use common Kotlin, with Kotlin/JS and Kotlin/Wasm adapters for Fetch hosts, Node.js servers, and HTTP functions. Core and HTTP are runtime-independent; adapters connect applications to host runtimes.
The API is experimental.
All adapters target Kotlin/JS and Kotlin/Wasm. Choose your hosting service, then add the module listed below. Application code uses the same runtime-independent Core and HTTP APIs on every host.
| Service | Runtime used by Koyane | Module | Example |
|---|---|---|---|
|
|
Cloudflare Workers runtime | koyane-cloudflare-workers |
Cloudflare Workers |
|
|
Node.js | koyane-lambda |
Lambda HTTP events |
|
|
Node.js | koyane-node |
Lambda HTTP server |
|
|
Node.js | koyane-node |
Cloud Run functions |
|
|
Node.js | koyane-fetch |
Vercel |
|
|
Supabase Edge Runtime (Deno) | koyane-fetch |
Supabase |
The runtime column identifies the runtime used by this implementation; services may offer other runtimes. Kotlin/Wasm runs through a JavaScript entry point within that runtime. Lambda Event Functions support API Gateway HTTP API and Function URL payload 2.0. Cloud Run functions use Google's Node.js Functions Framework. Compatibility is checked locally; deployment to these cloud services is not verified.
The following hosts can run the Node.js HTTP server on either Kotlin target. On virtual machines such as Compute Engine, run directly on Node.js or use a container. Container services run the same application packaged as a container image.
| Service | Runtime used by Koyane | Module | Deployment |
|---|---|---|---|
|
|
Node.js | koyane-node |
Directly or in a container |
|
|
Node.js | koyane-node |
Directly or in a container |
|
|
Node.js | koyane-node |
Directly or in a container |
|
|
Node.js | koyane-node |
Directly or in a container |
|
|
Node.js | koyane-node |
Directly or in a container, such as Docker |
|
|
Node.js | koyane-node |
Container |
|
|
Node.js | koyane-node |
Container |
|
|
Node.js | koyane-node |
Container |
|
|
Node.js | koyane-node |
Container |
|
|
Node.js | koyane-node |
Container |
|
|
Node.js | koyane-node |
Container |
|
|
Node.js | koyane-node |
Container |
|
|
Node.js | koyane-node |
Container |
|
|
Node.js | koyane-node |
Container |
|
|
Node.js | koyane-node |
Container |
|
|
Node.js | koyane-node |
Container |
|
|
Node.js | koyane-node |
Container |
|
|
Node.js | koyane-node |
Container; existing App Runner customers only |
These are hosting options for the Node.js server; service-specific deployment configurations are not included.
Icon sources: Diagrams, SVG Logos, Vercel, and Lucide via Iconify.
dev.quwac.koyane:koyane-bom aligns the versions of all Koyane library modules.
Import the BOM and add the modules used by your application without individual versions.
The BOM does not add libraries or install plugins automatically.
These snapshot coordinates require local Maven publication.
For a released version, use mavenCentral() and that release's BOM version.
The snippet below belongs in a Kotlin Multiplatform build targeting js, wasmJs, or both.
repositories {
mavenLocal()
mavenCentral()
}
kotlin {
sourceSets {
commonMain.dependencies {
implementation(project.dependencies.platform("dev.quwac.koyane:koyane-bom:0.0.1-SNAPSHOT"))
implementation("dev.quwac.koyane:koyane-cloudflare-workers") // Choose the module for your service above.
// implementation("dev.quwac.koyane:koyane-logging")
}
}
}All adapters expose HTTP and Core transitively.
For a runtime-independent library, use dev.quwac.koyane:koyane-http with the same BOM.
Source-based multi-project builds can use implementation(project(":koyane-http")) directly.
Install HTTP explicitly and return an HttpResponse from every handler.
import dev.quwac.koyane.core.koyane
import dev.quwac.koyane.http.Http
val app = koyane {
install(Http) {
get("/hello/:name") { text("Hello, ${param.string("name")}!") }
}
}Optional modules provide content negotiation, explicit JSON codecs, CORS, Bearer authentication, error handling, logging, date/time inputs, and in-memory application tests. See the cheat sheet for API examples and behavior.
Core and HTTP are independent of Fetch and host bindings. CloudEvents, SQS events, API Gateway payload 1.0, and ALB events are outside the HTTP adapters' scope.
The adapters have no database or driver dependency; applications supply their own database clients. Applications that need database access are expected to use Kagiroi as their database client. The current HTTP model uses buffered text bodies. Binary or streaming bodies, automatic request binding, OpenAPI generation, client generation, and a JVM server adapter are not part of this repository.