Forge
AI App Builder

Your internal system, built to fit and checked before you receive it

Describe the system you need in your own words — Forge builds it for you, and you try it in every role before your team uses it

You start from your own description: write in Arabic what you need — purchase requests, approvals, team notes or any internal workflow you run. It writes the contract in your language, shows the screens for each role and gives you the price before publishing. After your approval it becomes a real hosted app for your team.

Free Sandbox, no card · Lite from 249 SAR monthly · You know the price before publishing

104
credits — what a real requests system cost to build and publish; you see your own system's price before publishing
400
build credits every month with Lite
30
free credits in Sandbox — one time, no card
25
users per published app with Lite

How does it work?

From a description in your own words to a system your team uses, at a price you know before publishing

1
Describe your workflow in a conversation
Who requests, who approves, the deadline and who receives what, in your own words.
2
Forge writes the contract
Entities, fields, roles and workflows in a document the business owner can read and approve.
3
Review screens for each role, then the price
Hidden fields are absent from unauthorised screens. The price is one number, explained line by line.
4
Try it before you pay
An interactive preview with a test user for each role: enter your own test records and walk the whole cycle as a team member would.
5
Approve with a verification code, then it is published
Your approval covers the exact version you reviewed. Any later change needs a new review and approval.
6
Make changes later, with your data intact
A change is priced by what it adds or changes, with a minimum per change, and your data moves in one transaction or nothing does.

Three layers you can review

Forge gives you a contract you can read, one tested engine and a review before every release.

The contract
Read and approve it
Fields, states and permissions are documented for the business owner. Incomplete contracts are rejected before building.
The engine
One for all systems
No new code per customer: one tested engine enforces isolation, permissions, deadlines and approvals across all systems.
The review
Before every release
Before each release you see what will be published and its price, line by line, and approve with a verification code. Nothing is published without your approval.

Works alongside Nexus and Aria and Reach — for workflows beyond sales.

Features

A real internal system with permissions, approvals and history, not screens alone

Price before publishing
One number, explained line by line before you approve. It is held from your balance after your approval, and if the release does not complete it is not lost: it returns to your balance or is kept for a retry.
Screens for each role
Preview each role before publishing. Hidden fields are absent and actions appear only for authorised users.
A review before every release
See what will be published and what will change, line by line, and approve with a verification code from your phone.
Permissions and scopes
Own records, team records or all records. Hidden fields stay out of screens, lists, exports and history.
Approvals, deadlines and escalation
Steps, approvers, quorums and a deadline per step, with escalation to a higher role when late. Users cannot approve their own requests.
In-app alerts
An alert for whoever must act next, and one for the supervisor when a deadline is missed — inside your app.
Sealed audit history
Changes record who and when in a tamper-evident chain, without personal field values.
Changes priced by what they add or change
A change is never priced as a new app, and each change has a minimum. Anything that reveals or deletes data needs your explicit approval, line by line.
Your data belongs to you
Export your records from the app using readable names; each role exports only what it can see. Credits are for building and changing: running your published app does not use them.

How your system is priced

The price follows what your system contains, and you see it explained line by line before you publish. Among its lines:

  • Entities
  • Fields
  • States
  • Roles
  • Screens
  • In-app alerts

An edit after publishing is priced by what it adds or changes, never as the whole app again, and every edit has a minimum.

Examples of systems actually built

  • A requests system with 9 items104 credits
  • A team-notes system with an attachment84 credits
  • An edit after publishing: one field added10 credits

Any system you describe gets its own price, shown before you publish.

For comparison: Lite includes 400 build credits every month.

From the free Sandbox to Lite in three steps

Start with no card, and pay only when you want to publish your system to your team

  1. Sign up free

    Open your Sandbox account with no card: 30 one-time credits, one project and 60 chat messages.

  2. Describe your system and try it

    Describe your work in Arabic, see the screens for each role and learn its price in credits — all before any payment.

  3. Activate Lite and publish to your team

    For SAR 249 a month: 400 build credits every month and up to 3 published apps for your team, each for up to 25 users, with hosting included in the plan.

Questions, answered plainly

The real cost, payment, and what the app can do today

Does Forge only build certain kinds of system?

No. You do not pick from a list of ready-made systems: you write what you need in your own words — requests, approvals, team notes or any internal workflow you run — and Forge builds it from your description. You try it and see its price before publishing.

What does a release really cost in credits?

It depends on what your system contains, and you see the number before you approve. Real examples: a requests system with 9 items cost 104 credits, a team-notes system with an attachment cost 84 credits, and an edit that added one field cost 10 credits. Any system you describe gets its own price. Lite gives you 400 credits every month.

What happens if I stop paying?

There is no automatic charge: you pay each renewal yourself, and we remind you by email before the term ends. If the term ends and you do not renew, building and publishing stop; what you built is kept and returns when you renew. Hosting for your published apps is part of the paid plan.

Can I get a refund?

Write to support@enkorix.ai from your account email and mention the payment; we will review your request and reply. The suspension and termination clause is in the terms of use.

Terms of use

Start free and judge for yourself

In Sandbox you build your system and try it in every role before subscribing. The price is shown before each release.