FAQ
What serious teams ask before they sign.
Every answer here restates what is already on the site. Nothing is claimed on this page that cannot be checked on another one.
Getting started
What Redomic is.
- What is Redomic?
- Redomic rebuilds the software enterprises already run on, AI-native. An agent does the work inside the system instead of chatting beside it.
- Three legs, one core. Products we ship under our own name. A Studio that rebuilds one system inside your business. A Lab that measures what an agent can actually do in production.
- What is the difference between Products and the Studio?
- Products are ours. DevMesh is live in public beta, IntelliCode and NeuThera are built and public, and the AI-native ERP is in build. Everything on the Products page is Redomic's own work.
- The Studio is yours. It takes one system your business runs on and rebuilds it inside your operations, with your people in the room. The two never blur: a Studio build is not a product, and a product is not a Studio engagement.
- Who is Redomic for?
- Businesses that run on old software: the ERP, the ledger, the support desk, the operations tools designed decades ago around a person doing every step by hand.
- The reader we write for is a high performer buried in busywork. Every claim on this site ends in what that person gets back: time, focus, the morning.
- What does AI-native mean here?
- AI-enhanced software adds a feature to an old workflow. AI-native software rebuilds the workflow itself. Redomic only builds the second kind, and does the research that makes the claim credible.
Working with the Studio
How an engagement runs.
- How does a Studio engagement start?
- Before the spec. The first weeks are spent watching the work happen: which spreadsheet is the real system of record, which decision one person makes from memory. The spec is written together, from the work, with your operations lead and the people who do the job in the room.
- What gets built first?
- One workflow narrow enough to finish and real enough to matter, built end to end inside the systems you already run. Nothing gets ripped out. The legacy that has to stay stays.
- The new system runs next to the current process before it runs instead of it. Your people compare the two on their own work.
- Who owns the code?
- You do. The code, the decisions behind it, and a team that can carry it on after we step back. The data model is legible, the decisions are documented, and the handover is planned from week one.
- How long does it take, and what does it cost?
- We do not quote a duration or a price before we have read the work. A number given before that is a guess, and a guess on this page would be a claim we cannot show.
- Do we have to automate everything, or can we keep human control?
- You keep control. Every automated decision has an owner, a boundary, and a way to switch it off. Where the cost of being wrong is high, the system stops and asks. Where it is low, it acts and writes down what it did. Which is which is your call, and it stays a setting, never a rebuild.
Data and trust
What happens to your data, and what we can show.
- Where does our data go, and is it used for training?
- It stays yours, and it does not become training material for anyone else's model. We work inside the boundaries your organization already sets, in your environment where that is what your obligations require. Data placement is settled in the first week.
- What happens when the system gets something wrong?
- Someone finds out fast and sees exactly what happened. Every action leaves a record of what the system saw, what it decided, and what it changed. The system will be wrong sometimes. Reliability is the work of making that survivable.
- Do you hold a security certification?
- No. We hold no security certification today, and we are not going to imply that we do. Credentials go in the register on the Enterprise page as they are earned, named in full, scoped, and dated.
- Until then, send the security questionnaire you send everyone else. We answer it line by line, including the lines where the answer is no.
- Can we see references?
- We name no client we have not shipped for, and the Studio's proof section stays empty until real engagements exist. What you can look at today is on the Products page. Ask, and we show you a system running.
Philosophy
How we work.
- Is Redomic a real company?
- Open the products. Then ask us for a walkthrough of a system running. Seeing is the pitch.
- Why one category at a time?
- Rebuilding a workflow around an agent is a far bigger undertaking than adding a feature. It does not fit in a quarter. It counts when it is still running, and still trusted, a year after it shipped.
- Why do the research yourselves?
- You cannot rebuild a workflow around an agent without knowing what these systems actually do. The Lab measures how AI systems behave, learn, and hold up in production, and what it finds ships into every product and every Studio build. The papers and the products are the same work.
- Do you chase hype?
- No. We rebuild things that work, we put a real figure in a sentence only when we have one, and we show you a system running before we show you a deck.
Seeing is the pitch.
Bring us the workflow that eats your team's week. We'll show you what we would rebuild, and how it runs.