peekandpoke.io

What It Is

peekandpoke.io is not a single tool, but a set of open-source Kotlin libraries published on Maven Central under the coordinates io.peekandpoke.ultra. It is positioned as development infrastructure distilled from the authors’ own projects, covering dependency injection, serialization, immutable data mutation, reactive state, SPA development, a Ktor-based server-side framework, and data access for MongoDB/ArangoDB.

Core Capabilities

Kontainer is a lightweight DI container focused on request-scoped state management. It supports Singleton, Dynamic, and Prototype lifecycles, constructor injection, modularization, and dependency graph validation. Mutator uses KSP to generate mutators for immutable data classes, making it suitable for deeply nested objects, forms, and state editing. Kraft builds SPAs in pure Kotlin and is based on Preact under the hood, with a type-safe HTML DSL, routing, forms, state management, testing, and wrappers for several JS libraries. Funktor is based on Ktor and provides authentication, REST, background jobs, messaging, logging, Insights, static web serving, and testing tools. Monko, Karango, and Vault provide type-safe repositories, query DSLs, entity lifecycle hooks, and database abstractions.

Pricing and Open Source

The main text explicitly describes the project as open-source Kotlin libraries, with no mention of a commercial edition, hosted version, subscription pricing, or enterprise support. Its primary cost is therefore likely to be integration, learning, and ongoing maintenance rather than licensing fees.

Pros and Cons

The main advantage is its clear Kotlin-first design: DSLs, KSP code generation, type-safe queries, and compile-time validation run through multiple modules. It also offers strong consistency from the frontend with Kraft to the backend with Funktor and the database layer with Monko/Karango. The downside is that the ecosystem appears relatively niche, especially for the ArangoDB + Kotlin use case. While the documentation includes getting-started material and examples, there is little visible supporting information on community size, release cadence, SLA, or real-world production deployments.

Who It’s For

It is best suited to teams that make heavy use of Kotlin/Kotlin Multiplatform and Ktor, and that are willing to adopt a relatively unified technology stack. If you only need general-purpose DI, web development, or database access, mainstream options such as Koin, Dagger, Spring Boot, React, and the MongoDB Kotlin Driver have larger ecosystems.

Access from China

The main text does not provide information about access from mainland China, mirrors, payment methods, or compliance, so china_access can only be marked as unknown. Since the libraries are published on Maven Central, dependency retrieval will usually depend on local network conditions and Maven mirror configuration. If access to the website or GitHub is unstable, consider using Maven mirrors and evaluating alternatives such as Koin, native Ktor components, or Spring Boot.