What the base does

Igata is a workflow and agent-orchestration system for businesses that have no technical staff. Agents do a business's repetitive work as workflows. The business's own people approve what goes out and answer what the agents ask. The business pays for the work in credits on a plan.

The people who use it never see the machinery. They see three things: what needs them, what is running and what it cost. A model, a token, a prompt or a step graph never appears on a screen.

Why the name stays underneath

Igata never reaches a customer under its own name. One codebase and one platform company sit underneath market companies, and each market company runs its own deployment under its own brand, in its own country, in its own currency, on its own accounts. Noura is the first deployment, for Malaysia. Jemma is the planned second, for the United States.

A customer in Kuala Lumpur meets Noura, signs with Noura, pays Noura in ringgit and calls Noura for support. Nothing on that customer's screen, bill or contract says Igata. The name belongs to the partners, the lawyers and the engineers who stand behind those brands, and to the maker's mark on a licence schedule.

Brand as data

The same code runs every deployment. A deployment's whole face, its name, its persona, its portraits, its logo, its colours, its typeface, its copy, its locale, its currency and its channels, is one brand file. A technical identifier carries the platform's name or no name at all, and never a brand's.

That rule is what makes the mould a mould. A new market is a new brand file and a new deployment, never a new codebase. A rename is one file. A second brand proves nothing until the product sells without the founder's hands, which is why it waits until the first brand has a stranger's money.

What is agreed and what is open

Agreed: the platform company owns the code and the marks, and licenses them to each market company; each market company owns its customers and what it writes. Open: the second brand's timing, which follows the first brand's launch and not a date.

The next step is the first deployment, live for one customer, with real money in its ledger.

Three things

A person using an Igata deployment sees three things.

What needs them: a reminder to approve, a question to answer, two records that look like the same customer. What is running: the work in progress, as plain cards, each with its cost in credits. What it cost: the credits left on the plan and what each piece of work took.

Everything else exists and is never shown unless opened. The agents, the steps, the models and the prompts are there, doing the work, and a business owner has no reason to look at them. The only technical noun a customer ever meets is credits.

One name

Each brand has one named persona, the supervisor, and it is the only agent a customer meets by name. On the Noura deployment it is Noura. The specialists behind it, for marketing, sales, operations, research and engineering, are named in the code by their function and never on a screen.

A person approves what Noura drafted. A person answers what Noura asked. Nobody approves what marketing-agent drafted, because that is the system's word for the row and not the customer's word for the thing.

Simpler never means weaker

A page only hides what the function would refuse. A simpler surface never weakens who may approve what, because the gate lives in the runner and the outbox and not in the page. Nothing leaves a workspace in the customer's name without a person's yes or a standing rule the customer set, and every send records who or what authorised it.

The product never asks for a choice when only one is valid. Recovery belongs to the runtime: one automatic retry, then an incident for the market company's staff, so a person only ever sees questions that are real business decisions.

Why this is the product

The orchestration underneath is table stakes. What a business with no technical staff will pay for is the part they can see, understand and trust in the first minute. Every screen in every deployment is held to that: plain words, the customer's nouns, and nothing that needs a manual.

The next step is the walking skeleton: one workflow, end to end, that chases an overdue invoice, asks the owner before it sends, and shows what it cost.