OUR FOCUS / KSTL

C++ foundations,
thoughtfully built.

The useful pieces between the standard library and your next application.

KSTL brings reusable systems components into one evolving C++17 library. Built by kuku, an independent software development studio.

IN ACTIVE DEVELOPMENT / C++17 BASELINE
THE FOUNDATION STACK01 / STRUCTURE
YOUR CODEYour application
KSTLExtending, not replacing.LIBRARY
ConcurrencyNetworkingProcessesMemoryJSON / XMLAudio
C++17 + standard libraryPlatform services
Header-only by defaultShared runtime, when needed
C++17 language baselineWindows / Linux platform focusCMake integrationOne target. Two linkage modes.
01 / THE LIBRARY

Everyday systems work.
A more coherent toolkit.

Reusable building blocks for application developers who need explicit behavior, practical integration, and room to go deeper.

01executors / synchronization

Concurrency & execution

Task execution, synchronization primitives, and bounded and unbounded SPSC queues. Attention to ownership, shutdown, and resource lifetimes.

Make the lifecycle explicit.
02net / process

Networking & processes

Asynchronous I/O and process-management components for systems that communicate, launch work, and coordinate completion.

Connect work across boundaries.
03memory / container

Memory & containers

Memory utilities, buffers, and container extensions that complement the standard library rather than ask you to replace it.

Build on familiar foundations.
04json / xml / serialize

Structured data

JSON and XML documents, borrowed views, explicit editing, reusable output buffers, and conversion between data and C++ types.

Be clear about data and ownership.
05audio

Audio workflows

Audio components under active development, with ongoing work on asynchronous requests, capture notifications, and lifecycle handling.

Treat real-time boundaries carefully.
06system / filesystem / chrono

Platform essentials

System, filesystem, time, and text utilities for cross-platform application code, with platform-specific behavior made visible.

Keep portability grounded in reality.
02 / FITS YOUR BUILD

One public target.
Your choice of linkage.

Use kstl::kstl in your CMake project. Start header-only, or select the shared runtime when your application needs coordinated runtime state across modules.

CMake 3.19+ · C++17+
Platform and module dependencies still apply.

Ask about integration
CMakeLists.txt EXAMPLE / SIBLING DIRECTORIES
# my_app/ and kstl_lib/ live side by side
cmake_minimum_required(VERSION 3.19)
project(my_app LANGUAGES CXX)

# Header-only is the default
add_subdirectory(../kstl_lib kstl)

add_executable(my_app main.cpp)
target_compile_features(my_app PRIVATE cxx_std_17)
target_link_libraries(my_app PRIVATE kstl::kstl)
No separate KSTL runtime binary is required in header-only mode.
03 / HOW WE BUILD

Engineering before promises.

A library earns its place through understandable interfaces and repeatable checks—not a headline benchmark.

[ 01 ]

Explicit contracts

Document ownership, error handling, cancellation, and lifetime boundaries alongside the code.

[ 02 ]

Testable behavior

Develop regression tests, runnable examples, and focused checks for concurrency and compatibility.

[ 03 ]

Honest portability

Distinguish supported compiler baselines from unverified configurations. Make integration constraints clear.

PROJECT STATUS

Actively evolving, deliberately scoped.

KSTL is under ongoing development. APIs and module coverage may change. Documentation, examples, and validation evolve with the implementation.

PROJECT OVERVIEW
INDEPENDENT BY DESIGN

Small studio.
Deep technical work.

kuku is an independent software development studio focused on reusable C++ infrastructure. KSTL is our current core project: an effort to bring practical systems components together with consistent integration and clearer contracts.

We build on established C++ ideas and libraries, with attention to attribution, compatibility, and the boundaries of each implementation.

LET’S TALK ENGINEERING

Building something
with C++?

For KSTL questions, technical feedback, or collaboration inquiries.

CONTACT THE STUDIOkuku@startfreeai.comDirect email. No sign-up required.