Documents were missing from the list
There were 13 documents that day; the list showed 1. Three item filters in a saved query narrowed it. No code change.
Your user writes the problem in Slack, in plain language. Your consultant, working with AI, reads your business data, the TROIA source code and the trace at once, finds the root cause and puts the fix in the test environment. Going live takes your approval.
No credit card · no commitment · Canias 8.03 and 9.03
The withholding columns come up empty, I can't issue the invoice.
The trace can't find the VAT key. The definition has zero-three; it should be the letter O. Fixed in both companies.
Classic consulting has a wait between every step: explaining, queueing, asking for a trace. Here those gaps are gone, and the gate to production stays with you.
Your user writes in the Slack channel in their own words; the request becomes a ticket automatically.
Business data, TROIA source code, the trace and the compiler are read at once.
The root cause is found down to the line; development happens in an inherited object.
The change goes to the test environment with a backup; what changed is written down.
It goes live only with your written approval, and can be rolled back.
No trace requests, screenshots or email threads. Users write the problem and get the answer in their own language.
Error messages aren't guessed: the code line behind the message is opened, the condition read, the data measured.
Development in inherited objects, the standard stays intact. Writes to production are backed up, measured and approved.
Questions are unlimited; development jobs run in parallel, up to three at a time.
Every request is in the portal: history, test, approval and proof. Your team watches the office live.
Runs on a single service user and leaves your users' licences alone.
Each company gets a lead and parallel developers. Your team watches the office in the portal: who is on which request, the last step, who is waiting for your test. Status refreshes every 15 seconds; if data is stale, the screen says so.

Requests came in on Slack and each became a ticket in the portal. The numbers are from that company's records.
From request to the test environment: median under an hour. Going live depends on the customer's test and approval.
There were 13 documents that day; the list showed 1. Three item filters in a saved query narrowed it. No code change.
All 185 flagged rows had arrived by transfer. Each row's path was shown from the data and new columns were added; totals unchanged across 6,956 rows.
Before switching the log on, yearly volume was measured per table in test. The decision went to the customer with numbers.
We searched live data for rows already breaking the rule: 27 rows deleted but already issued from stock, listed by document number.
One line after each valuation; the same day a five-account comparison: “all clear” or a difference list with document numbers.
The trace showed the error in the document itself: the counterparty had both accepted and rejected the same goods. The right path was a return note; no code fix needed.
The definition said zero-three where it should have said the letter O. The mechanism had never worked for three years; fixed in two companies at once.
The customer asked for a button on the account screen. The classic path means IDE, VPN, a licence and an available consultant. We did the whole job through Canias's own service layer, without a single direct database connection.


The drawings are not screenshots; they were generated from the screen's own geometry. The standard object is unchanged, so there is nothing to overwrite on a version upgrade.
Read the full button case →Questions are unlimited on all three plans; no counter per question, hour or day. What separates them is what the consultant may do in your system. Up to three development jobs run at the same time.
Prices exclude VAT; cancel any month. The subscription covers ongoing work; new module rollouts, data migrations and large projects are quoted separately. Setup takes half a day: a Slack channel, read access to the database and the trace folder.
Canias 8.03 and 9.03. Setup needs a Slack channel, read access to the database and access to the trace folder.
Nothing goes straight to production. Test environment first, with a backup and a compile check; production only with your written approval, and it can be rolled back.
Yes, there is no counter on questions, analysis or follow-up. Development jobs run in parallel, up to three open at a time.
No. No IDE is opened in day-to-day work; everything runs through a single service user.
No. AI speeds up reading and analysis; decisions, development approval and go-live stay with the consultant and with you.
First 7 days free. No credit card, no commitment.