Get demo access

Know your
Creatio

ctx10 indexes every instance you connect, every process, rule, page, field and role, and what depends on what. Ask it what changed last week and the answer comes back dated, with a name against every line.

Run it on your instance →

Read-only. Nothing is ever written back to your Creatio.

Not ready to connect yours? Try it on stock Creatio 10X →

How it works
01
Pipeline

Set up your pipeline

Connect development, pre-production and production. ctx10 reads each one and builds an index of every process, rule, page, field and role in it. On the 8.3.4 instance we verified against, that came to 425 packages and 1,326 code edges — which is what turns what breaks if I rename this field into a question with an answer. Put it on a schedule and the index stays current.

02
Checks

Every index, checked

Every index gets checked and the findings are ranked. Three processes that all start on every new Lead, in no guaranteed order, or a process waiting for a change to a field that was deleted, so it will never run again. When a check cannot run against your instance the report says so instead of marking it passed.

03
Release reports

Ship a release report

Compare production against pre-production and get a dated, watermarked report of what changed. Anything that reached production without going through the pipeline is listed on its own.

04
Ask

Ask it anything

Search the index yourself, or mount it in Claude, Cursor or Codex and let the agent ask. Before it renames a column it can find out what reads that column, from your real configuration rather than a guess at what the field is probably called.

ctx10 · pipeline · acme ● read-only
Development Index #34 ✓ indexed · 2h ago
Pre-production Index #31 ✓ indexed · 1d ago
Production Index #34 Stage 24 of 25 · 96%
247
Entities
4,812
Columns
162
Processes
89
Pages
reads configuration only · never writes back re-run on a schedule
ctx10 · checks · index #34 4 high · 11 medium
HIGH
Runs twice · duplicate triggers
Every Lead that is created is handled by all 3 of these at once, in no guaranteed order.
HIGH
Dead automation · waits on a deleted field
This automation waits for a change to a field that no longer exists. That change can never arrive, so it can never run.
MED
Runaway loop risk · fires on every save
This automation re-runs on every single save of every Order. 4 other automations already start on this record, so this is how runaway loops start.
ctx10 · release report · prod ⇄ pre-prod 7 changes
production · #34 ⇄ pre-production · #31
  • + UsrDiscountOverride process not in pre-prod
  • ~ LeadProcessing process version published v2 · lineage tracked
  • ~ Opportunity.Amount column read by 2 more processes
  • − Auto-assign owner business rule removed in production
3 of 7 reached production outside the pipeline · dated · watermarked
claude · @ctx10/index mounted MCP
You
I’m about to change Opportunity.Amount. What breaks?
Claude · via @ctx10/index
→ impact_of("Opportunity", "Amount", "rename") → run_checks("duplicate_triggers")

12 things depend on it: 5 processes, 3 pages, 2 business rules, 2 schedules. The ones to watch:

  • Recalculate amount: writes it on every stage change
  • Pipeline dashboard: 3 widgets read it
  • Approval over 50k: a business rule gates on it

Also: 2 processes fire on the same trigger, so every opportunity is scored twice.

Who it’s for

Everyone who gets asked questions about your Creatio

Consultants using AI tools

Point Claude, Cursor or Codex at your real configuration, so the field names in its answers are ones that exist.

On-call engineers

When a process fails at 3am, ctx10 matches the trace against the index and names the step, instead of handing you the log.

Architects planning changes

Before you change a field, see every page and process that reads it, listed before you start.

New team members

Learn the instance by clicking through the index, and ask the agent when a process does not make sense. Nobody has to keep a wiki current.

Release managers

Compare production against pre-production before you sign off, and see what went live without passing through a release.

Risk & internal audit

Every change with a date and a name attached, including the ones an AI agent made under a person’s login.

Frequently asked

Questions teams ask before they try it

What is ctx10?
ctx10 reads the configuration of your Creatio and builds an index of every process, rule, page, field and role in it. The checks run against that index. So does the comparison between two indexes that shows what changed between a release and the one before. You browse it in the app, and an AI agent can read the same index over MCP.
Does it change anything in my Creatio?
No. The add-on that runs inside your Creatio accepts one kind of command, a read, and refuses everything else before it reaches the database. The database session it uses is read-only as well, and is rolled back after every read even when the read succeeded.
What does it find?
Processes that both start on the same event and do the same work, and processes that wait for a change to a field that no longer exists and so can never run. It shows how many things read a field before somebody renames it. Changes that reached production without going through a release are listed too. Findings are ranked, and if a check could not run on your instance the report says so rather than marking it passed.
Doesn't Creatio already log changes?
Creatio keeps a change log for one instance, and it does not know what depends on what, so it can tell you a process was edited but not what that edit affected. It also cannot tell a person from an AI agent working under that person’s login. ctx10 keeps dated indexes of every instance you connect and compares them, so the same edit shows up with what it touched and whether it went through a release.
How long does it take?
A few minutes on a small test system, and up to an hour on a large production with hundreds of packages. You re-run it whenever you want a fresh index, or put it on a schedule.
What does it cost?
$1,000 a month, or $10,000 a year, per organisation. One organisation means its whole Creatio, every instance it runs, indexed as often as you like, with no limit on seats or queries. The only thing metered inside a subscription is AI mode, which is off unless you ask for it and includes 1 million tokens a month. There is a 30-day money-back guarantee. See the Pricing page.
Which AI tools work with it?
Anything that speaks MCP, which today means Claude, Cursor, Codex and the smaller clients like Continue and Cline. The agent asks ctx10 what a change would break before it makes it, and nothing about that ties you to one tool. Answering over MCP never calls an AI provider: your agent is reading your index. AI mode, the chat on the Ask page, is the only part of the product that calls one, and it is off until you ask for it.
Is my data safe?
We read configuration, not records. Contacts, accounts, leads and orders are never captured. One configuration table we do read is Creatio's own list of users, and the capture query leaves out its email, phone and password columns, so those values never leave your Creatio. The index we build for you lives in a database of its own and every query against it is scoped to your workspace before it runs. We do not train AI on any of it. The Security page has the detail.

Run it on your instance.
See what it finds.

Thirty minutes, read-only, on a test copy or your live system. You keep the report whether you buy or not.

Which instance?
What are you trying to find out? pick any

We use these details to reply and for nothing else. No newsletter. They are kept 24 months from your last message and then deleted. See Data & privacy.

Read-only · nothing is ever written back · nothing to pay for the thirty minutes