Skir: Modern serialization format and code generation tool.

What it does

Skir is a schema language and code generation tool that lets developers define data types and APIs once in a declarative format, then automatically generate type-safe code for multiple programming languages. A developer writes a schema in a .skir file and Skir generates idiomatic code for TypeScript, Python, Java, C#, C++, Kotlin, Dart, Swift, Go, Rust, Zig, Gleam, and MoonBit. The tool includes a watch mode that regenerates code on every schema change, and runs as a zero-install compiler via npx.

Who it is for

Skir targets teams building distributed systems, APIs, or microservices that need to maintain consistency across multiple programming languages. It appeals to organizations using LLM-powered coding tools, since the homepage claims strong typing reduces type-related coding errors. Teams managing long-lived systems where schema evolution matters would also benefit from its built-in compatibility checking.

Pricing

The site does not show prices.

How it stands out

Skir presents itself as a modern alternative to Protocol Buffers, with emphasis on simplicity. All configuration lives in one YAML file and initialization requires a single command. The tool generates immutable types with all fields required at construction, supports polymorphism through sum types with typed payloads, and offers multiple serialization formats (JSON and binary). SkirRPC provides a lightweight HTTP protocol for type-safe cross-service communication with a built-in Studio app for testing. Developers can import types directly from GitHub repositories rather than copying files.

What a founder should check

An engineer building a competitor should verify: First, how entrenched is Protobuf in the target market, and what switching costs do existing users face? Migration from Protobuf requires regenerating all dependent code and retraining teams on a new syntax. Second, whether Skir's language support advantage holds long-term—Protobuf dominates in gRPC ecosystems and enterprise environments where GCP, AWS, and Java shops predominate, and adding more language backends doesn't guarantee adoption if platforms favor established tools. Third, the pricing model and sustainability question: if Skir remains open-source and free, revenue becomes a constraint on long-term maintenance and community support versus proprietary or SaaS competitors.

Thinking of building something like this?

Every launch here is a competitor to somebody's idea. If yours is close, check it against the market before you build: the Full Check names the rivals, the prices and the gaps.