Roadmap
What's coming next
A look at the direction Mélodium is heading. These items are ordered by priority, from what is coming first to what follows.
- 01Up next
Secrets as a datatype
A dedicated Secret datatype, such as Secret<string>, to hold sensitive values such as API keys and credentials. It flows through treatments like any other value, while staying out of logs, traces, and serialized data.
Secret<string> - 02
Documentation per package
Mélodium currently has a single global documentation, covering the whole language and standard library. Each package will get its own reference instead, generated per package and per functional area, through a dedicated documentation generation tool paired with an online service to browse and host it.
Browse the current documentation - 03
Resources in programs
Resources will become a first-class element kind of their own, alongside treatments, models, and functions. Programs will be able to declare and inject external resources, such as files, connections, or configuration, with the same standing as any other building block.
- 04
Python support
Mélodium already supports writing treatments in JavaScript alongside Rust ones. Python support will follow the same model, letting existing Python libraries and teams connect directly into Mélodium dataflow programs.
- 05
WebAssembly-compiled packages support
Compile and load packages as WebAssembly modules. Packages become portable and sandboxed, running anywhere the engine does, independent of the host platform.
- 06
Packages registry
A central place to publish, discover, and version Mélodium packages. Sharing treatments and models across projects and teams becomes straightforward.
Development happens in the open, and updates are shared regularly.