Philosophy
Open by Design.
Codcel is a small, independent company with no external funding. We're growing the simple way: by building something genuinely useful and earning the trust of the teams who use it.
Openness isn't a marketing slogan for us – it's how the product is built. You get real source code, open engines, and a clear bridge between business and IT.
- No black boxes
- Full source code, no proprietary runtime, and no hidden engines you can't inspect.
- Real production code
- Rust, Python, Java, C#, TypeScript, Go, Swift, and more – ready for your CI, not trapped in a tool.
#[test]
fn test_codcel_quotation() {
let output = codcel_quotation(&QuotationInput {
car_model: "5 E-Tech".to_string(),
car_version: "52 kWh".to_string(),
car_make: "Renault".to_string(),
postcode: "RG6 1WG".to_string(),
insurance_type: "Fully Comprehensive".to_string(),
windscreen_cover: true,
liability_limit: "25 Million".to_string(),
age: 41.0,
}).unwrap();
let result_total_premium = output.total_premium;
assert_eq!(result_total_premium, 420.07);
}Full source code, not a black box.
When you generate a project with Codcel, you don't get a frozen artifact or a proprietary runtime. You get real, human-readable source code that your developers can review, test, and extend.
No proprietary runtime
Codcel-generated projects run as normal applications in your stack. There's no hidden interpreter or runtime that only we control.
Built for long-term ownership
If you ever stop using Codcel, your code keeps working. You can move it to another team, another vendor, or another cloud without asking our permission.
Built on Rust at the core.
All of our core engines are written in Rust. We chose Rust because it gives our customers – and our own engineering team – real advantages.
- Performance– fast and predictable, ideal for heavy financial and business logic.
- Safety– memory safety and strong typing eliminate entire classes of runtime bugs.
- Code quality– a modern toolchain and strict compiler keep the core clean and consistent.
- Maintainability– structured, well-tested libraries that can evolve safely over time.
The same engineering discipline we apply to our Rust core shapes the quality of the code we generate for your stack.
Open core engines, used by your code.
To keep everything transparent, we've built core engines that are themselves open source. Codcel-generated projects use these libraries directly – there's no mystery box.
- Codcel Calculation Engine
- An Excel-compatible calculation library implementing functions as real Rust code. Your generated projects call into this directly, so you can see exactly how numbers are computed.
- Codcel Table Engine
- Handles table lookups, joins, and mappings in a clear, inspectable way – no hidden VLOOKUP magic living on a server you don't control.
- Open documentation
- Even our documentation is open. We want the community to help us refine patterns, improve examples, and push the ecosystem forward.
Roadmap: where Codcel is going next.
We're still early, but we're moving fast. Our goal is simple: Excel-level expressiveness, production-grade code, and first-class support for the stacks you run today and tomorrow.
Excel Function Coverage
Rapidly Expanding Excel Engine
Codcel now supports 464 Excel functions — and we're still shipping fast.
Every release expands compatibility, improves precision, and closes edge-case gaps so your models behave exactly as they do in Excel.
Our goal isn't partial support. It's full Excel expressiveness — translated into production-grade code.
A complete, searchable list of supported functions is available in the documentation.
Files, languages & platforms
From one workbook to many
Today Codcel focuses on a single Excel file per project, which keeps things simple for the first release. Next, we plan to support linked Excel files so larger models with multiple workbooks can be converted into a single, coherent codebase.
More languages
Our starting point is strong support for languages like Rust, Python, Java, C#, TypeScript/JavaScript, Go, and Swift. Over time we plan to add more languages and refine each generator so the output matches idiomatic patterns in that ecosystem.
More platforms
We're also exploring additional platforms: serverless targets, containerised deployments, and deeper integrations with common CI/CD setups. The goal is for Codcel projects to slot naturally into the way your teams already ship software.
Roadmaps change as we learn from customers, but the direction is stable: more Excel compatibility, more languages, and more control in your hands.
Early version, long-term mindset.
This is our first public version of Codcel. There will be rough edges – and we're committed to fixing them quickly, in the open, together with the teams who use us.
If you care about open, inspectable, high-quality software instead of opaque platforms, we'd love you to be part of this journey.