One set of rules, inherited down the portfolio.
The masterbrand sets the frame; sub-brands inherit it and record their own decisions against it. One record spans the portfolio, so a question about any brand has one answer.
Enterprise
Governance that names names.
Built for MENAT enterprise portfolios. Verdicts name reviewers. Roles carry limits. Every decision leaves a record.
Your choice of models,on your keys,with every draft checked before it ships.
Usage on your keys does not count against plan limits.
Your models. Your keys. One gateway.
Every place NeoIQ calls a model runs through a single admission point, so the provider is a setting rather than a rewrite — and usage on your own keys never touches plan limits.
One gateway
Every model call goes through one gateway, on your keys.
95%
of companies have brand guidelines. Only 25–30% enforce them consistently. The problem is enforcement, not knowledge.
1.75×
the media spend inconsistent brands need to reach the same effect, per System1 and IPA research (2025).
Brand Guard
Four tiers. One rule: risk sets friction.
Brand Guard reviews every output. A verdict names the issue, the failed rule, and the human reviewer. Higher risk meets greater friction — guardrails, not gates.
Enforcement
Pick a tier and what each one does to a draft.
- Verdict
- Blocked
- Defaults
- Regulatory and identity rules
- Behaviour
- Hard block. The output does not ship until the rule passes. There is no override.
A verdict, in product
Every verdict names the issue, the rule and the human.
Nothing ships unapproved.
Usage
You see the ceiling coming turns amber at 80%, red at your cap.
Six things are metered and nothing else. Overage is capped in USD per month, at a number you set. The breakdown exports as CSV — model, provider, tokens, requests, estimated cost.
Diagram, not telemetry
A PDF is not a control.
A brand book explains appearance. A system governs behavior. NeoIQ turns your guidelines into live rules that every output passes through.
Portfolio
Masterbrand and sub-brands, one system.
One set of brand rules can govern a portfolio. The masterbrand sets the frame; sub-brands inherit it and record their own decisions against it.
See how the rules work
Three levels of rules
Portfolio holds the masterbrand and its sub-brands. Identity holds each brand's strategic and visual rules. Operational holds the campaigns, calendars, and variants that fill in over time. Sub-brands inherit what the masterbrand locks and own what it leaves open.
Roles with limits
Six built-in roles, custom roles, and access groups that give a set of people the same permissions. Exactly one Primary Owner. Only Owners manage roles, billing, SSO, and deletion. Owner · Admin · Billing · Member · Viewer · Guest.
Adoption
From brand book to live rules in a week.
No migration project. No workshop series. NeoIQ ingests the guidelines you already have and turns them into a working system.
Day 1
Onboard the brand
Start from your homepage URL or upload the brand book. Under an hour later, publishing turns on the rules, the checks, and every workspace at once.
Week 1
Run the first campaign
Brief, draft, review, approve, ship — in both languages. Every output passes Brand Guard, and every approval leaves a receipt.
Ongoing
Keep the rules current
Small changes are targeted edits. A repositioning re-runs the whole thing — creating a new version, never overwriting the old one. The audit log holds the whole history.
Security
Enterprise controls, named and scoped.
Security controls your IT team will recognize, with usage controls your finance team will ask for.
SSO with domain verification
OIDC and SAML 2.0. Verify your domain over DNS, map your identity provider's groups to roles, and provision seats with SCIM.
2FA and scoped API keys
TOTP with backup codes. API keys are shown once, carry scoped presets, and expire — 90 days by default.
An audit log that names names
Every approval, override, and handoff is recorded with the operator who made it. Export usage as CSV.
Your model keys, your rules
Bring your own provider keys (OpenAI, Anthropic, Google, Mistral, Azure, AWS). Set a monthly spending cap in USD.
Bilingual
Arabic as a peer, by rule.
Arabic is built in, not bolted on. These rules apply to everything NeoIQ ships.
- 01Arabic is a peer, not a translation layer. English is written knowing Arabic sits beside it.
- 02Verbs mirror exactly — Approve is اعتماد, everywhere it appears.
- 03Western numerals by default; Arabic-Indic numerals are a setting each organization turns on.
- 04Arabic is never letter-spaced. Line height runs 1.7 to 1.8.
- 05Native MENAT review before anything Arabic ships.
EN
Approve
AR
اعتماد
The same verb, mirrored exactly. Language changes the whole interface — navigation, buttons, how the agent speaks — not just the copy.
Where it runs
Your data, your jurisdiction.
[PLACEHOLDER SECTION — the regions, providers and frameworks below are unfilled. NeoIQ production runs from eu-west-1 today; nothing here ships until the regions and certifications are confirmed.]
[REGION — e.g. United Arab Emirates]
[PROVIDER REGION]
[CITY]
[FRAMEWORK][FRAMEWORK][FRAMEWORK]
- [GUARANTEE]
- [GUARANTEE]
- [GUARANTEE]
[REGION — e.g. Saudi Arabia]
[PROVIDER REGION]
[CITY]
[FRAMEWORK][FRAMEWORK][FRAMEWORK]
- [GUARANTEE]
- [GUARANTEE]
- [GUARANTEE]
European Union
AWS eu-west-1
Ireland
[FRAMEWORK][FRAMEWORK][FRAMEWORK]
- [GUARANTEE]
- [GUARANTEE]
- [GUARANTEE]
Built for teams with the strictest review requirements
Encrypted in transit and at restScoped keys that expireEvery decision attributedDedicated deployment available
Bring your own cloud
Deploy into your own account.
For teams that need the infrastructure inside their own perimeter, NeoIQ deploys as a dedicated install — its own account, cluster, database, storage and domain, separate from ours.
Your security perimeter, your rules
Your compliance regime, not ours
Your account, your data, your keys
[CONFIRM which of these NeoIQ supports today]
Private beta
Bring your portfolio.
NeoIQ is in private beta with MENAT enterprise teams. Tell us about your brands, your markets, and your review process — including deployment requirements.
Talk to us