← the front page · Support
Getting help
There are two ways to get help with Raku++: the public issue tracker on GitHub, open to everyone, and commercial support for organisations that want agreed response times and engineering time of their own.
GitHub issues
A bug, wrong output, a module that will not install, or a question about
how something behaves: open an issue in the Raku++ repository. It helps
to include what rakupp --version prints, the smallest
program that shows the problem, what it printed and what you expected.
Open the issue tracker →
Commercial support
Support agreements with set response times, fixes and features on demand, help moving code from Rakudo, performance work, builds and training — from DeepSoft, the team that develops Raku++.
What it includes →
For organisations
Commercial support #
Raku++ is open source and free, and it stays that way. If your organisation runs Raku in production — or is deciding whether to — you can also have the people who build the engine on your side: someone to call when something breaks, fixes delivered on a schedule you agreed, and engineering time for the parts of the language your code leans on hardest. Support is offered by DeepSoft, the team that develops Raku++.
Pick what you need
What we offer #
Most engagements combine two or three of these. None of them is a fixed package: we start from your code and your constraints, and shape the work around them.
Support agreement #
A named contact, response times written into the agreement, and your reports at the front of the queue. A fix arrives as a patch release you can deploy.
Fixes and features on demand #
A construct your program needs, a behaviour that differs from what you expect, a module from the ecosystem that will not install — scoped, estimated and implemented, with tests that keep it working in every later release.
Moving existing code #
Already running Raku on Rakudo, the reference compiler? We run your code base and its test suite under Raku++, report every difference we find, and close the gaps — so the move is measured before it is made.
Performance work #
We profile your real workload, not a benchmark, and make the engine
faster where your program spends its time — or show how
--exe, parallel workers and native types change the
picture for it.
Embedding and integration #
Raku inside your own product: the engine as a library linked into an application, as WebAssembly in a web page, or as a standalone executable shipped to machines with nothing else installed. We design the boundary with you and keep it working.
Platforms and builds #
Builds for the platforms and toolchains you deploy on, size-trimmed builds for constrained targets, and a maintained release line that receives fixes without new features when stability matters more than novelty.
Training #
Courses in Raku for your developers, from a first introduction to grammars, concurrency and the object system — taught by the people who wrote the engine and the Raku Course.
Code review and consulting #
A second opinion on a Raku code base or on a plan to adopt the language: where it fits, where it will hurt, and what to measure before deciding.
Something else #
If what you need is not on this list, ask anyway. The engine, its compilers and its tooling are all written by the same team, so very little is out of reach.
From the first e-mail
How it works #
1. A conversation
You tell us what you run, what worries you and what you would like to be true a year from now. No forms and no obligation — just a call or an exchange of e-mails.
2. A look at the code
Where it helps, we run your programs or their tests under Raku++ and tell you what we see. Code you share stays confidential, under an NDA if you want one.
3. A proposal
A written scope with the work, the response times and the price — a fixed price for defined work, or a retainer for ongoing support.
4. The work, measured
Every change goes through the same release gates as the rest of the engine — the official test suite, the ecosystem's own test suites and the performance guard — so fixing one thing does not quietly break another.
No lock-in
What stays open #
Raku++ is released under the Artistic License 2.0, and commercial support does not change that: the engine you build on stays open source, so your code is never tied to a single vendor.
Whether a particular fix or integration goes into the public releases or stays in a build of your own is part of the agreement, and we settle it with you up front.
Let's talk
Get in touch #
Write to mail@deepsoft.online with a few lines about your organisation and what you use Raku for, or plan to. You will get an answer from an engineer, not a sales funnel.
Write to us DeepSoft's page Where Raku++ stands today
DeepSoft is a software company registered in the Netherlands (KvK 83163271). Contact details: deepsoft.online/contacts.