GDT
PLANNED
Kalpi for Godot
Godot integration for input, saves, cartridge identity, metadata and export validation.
View preview →KALPI FOR DEVELOPERS / PLATFORM PREVIEW
BUILD DIGITAL.
SHIP PHYSICAL.
Use the engine you already know. Build your game, test it for Kalpi and turn a finished master into a real cartridge release.
PLATFORM STATUS
IN DEVELOPMENT
PROFILE
DRAFT 0.1
01 / Engine support
Your engine. Kalpi's platform layer.
Our goal is to make Kalpi feel familiar to developers. Engine integrations will expose the same core platform services while keeping the workflow native to each tool.
UNT
PLANNED
Kalpi for Unity
Unity package exposing the Kalpi runtime services and physical-release workflow.
View preview →UNR
PLANNED
Kalpi for Unreal
Unreal plugin targeting the same Kalpi APIs through engine-friendly components and tooling.
View preview →SDK
PROPOSED
Kalpi Native SDK
A lower-level route for custom engines and frameworks such as SDL, C++ and similar workflows.
Platform preview →02 / Common platform layer
One small API surface.
The exact implementation is still being designed. The intention is that every supported engine maps to a common set of Kalpi services.
Kalpi.SystemSystem state and platform informationKalpi.InputControllers and local playersKalpi.SavePortable game-save servicesKalpi.CartridgePhysical game and release identityKalpi.MultiplayerLocal multiplayer helpersKalpi.MetadataGame, build and release metadataAPI names shown here are design previews, not a released SDK contract.
03 / Platform profile
Target Platform Profile / Draft 0.1
We want developers to see the platform take shape without pretending unfinished hardware decisions are already final.
PLATFORM PRINCIPLES
Defined direction
- Physical cartridge is the game
- Offline-first operation
- No mandatory player account
- No runtime DRM authentication
- Local multiplayer as a platform priority
- Cartridge-based game and release identity
- Frozen mastered physical releases
- New fixes become new physical releases
UNDER VALIDATION
Technical targets
- Display modes and resolution targets
- Frame-rate targets
- Memory budget
- Game package capacity
- Save capacity and storage architecture
- Controller specification
- Audio formats
- Graphics API
- Boot-time requirements
Why no numbers yet?
Because those numbers should come from prototypes and testing, not marketing copy. When a target is validated, it moves into the published platform profile.
04 / Developer workflow
From project file to physical release.
01BUILDYour engine
→
02EXPORTFor Kalpi
→
03TESTRuntime / hardware
→
04VALIDATEPlatform checks
→
05MASTERFrozen build
→
06MANUFACTUREPhysical run
PHYSICAL RELEASE
KLP-027 · R1
THE CARTRIDGE IS THE VERSION.
05 / Kalpi Dev
The developer kit we're designing.
PLANNED
Kalpi SDK
Common platform APIs and runtime integration.
PLANNED
Engine Plugins
Godot, Unity and Unreal integrations.
PROPOSED
Desktop Runtime
Test Kalpi-targeted builds during development.
PROPOSED
Validation Tools
Check metadata, platform rules and release readiness.
PROPOSED
Package Builder
Create a masterable Kalpi game package. Final format is not yet defined.
FUTURE
Cartridge Tools
Physical development and mastering tools once cartridge architecture is validated.
06 / Documentation
Follow the platform as it becomes real.
The developer docs distinguish platform principles, proposed interfaces and technical decisions that are still under validation.
07 / Early developer interest
Building something interesting?
Tell us what you're working on. Early developer feedback will help shape the tools, constraints and publishing workflow.