How it works

What Forenta is and what it gives you.

Forenta assesses what you provide about your product and gives it structure. Forge gives you a verdict and a next step. Forenta Enterprise wraps a pipeline with stages, roles and checks around it, for now as a pilot.

What is Forenta?

A place to work, an engine and a pipeline.

  • A place to work

    Forenta is an online platform you sign in to. Your idea, the analysis, your projects and the collaboration live in one place, so nothing gets lost in loose chats.

  • An analysis engine: Forge

    Paste an idea, copy, plan or relevant code context. Forge assesses what you provide and returns the core, the risks and a concrete next step. It does not import a URL or repository by itself.

  • A pipeline: Forenta Enterprise

    With Forenta Enterprise, a production pipeline wraps around that same analysis: eight stages with a decision point between them, roles and permissions, a monthly budget for model usage and an audit trail.

Who it is for

One way of working, two ways to use it.

Builders

Forge

For founders, developers and freelancers who build themselves. Paste an idea, concept or relevant code context into Forge, get a verdict and continue with the plan in your own environment. During the beta you use Lite; paid plans are still off.

Organizations

Forenta Enterprise

For teams that move AI and software initiatives from idea to execution under control. The same analysis, now with eight stages, decision points, roles and permissions, a monthly budget and an audit trail around every project.

Inside a stage

From project context to executable build instructions.

At Forenta, product development is not a single loose AI prompt. Each stage starts from what is already there: project context, earlier decisions, findings and evidence. A fresh analysis follows. The outcome is turned into actions, checks and build instructions for the next step.

  1. 01input

    Context and evidence

    Project context, earlier decisions, findings and evidence form the input for the stage.

  2. 02analysis

    Structured analysis

    That context is assessed from several angles, such as product, engineering and security.

  3. 03verdict

    Findings and verdict

    The analysis produces concrete findings and a reasoned verdict.

  4. 04actions

    Tasks and recommendations

    The verdict is turned into tasks and recommendations for the next step.

  5. 05gate

    Required checklist

    A checklist per stage guards quality. Until it is done, the stage cannot move on.

  6. 06artifact

    Stage artifact

    Each stage records an artifact, from project brief and blueprint to test and monitoring report.

  7. 07output

    Build prompt

    An executable build prompt turns the outcome into instructions for the next step.

  8. 08review

    Review and stage transition

    A person reviews the outcome. Only after sign-off does the project move to the next stage.

Continue in your own development environment

For each stage, Forenta provides context, tasks, checks and a build prompt for your own environment: Claude Code, Codex or another AI tool. Through MCP, Claude Code and Codex write results and evidence back to the project for the next review.

  1. Analysis in Forenta
  2. Build prompt and checklist
  3. Claude Code, Codex or your own tool
  4. Implementation
  5. Result and evidence back to Forenta
  6. Review of the next stage

The handover uses build prompts, Markdown, tasks and documents. In Forenta Enterprise you can connect Claude Code or Codex directly. Both read the project context and can report work with evidence, handle findings, tick checklist items and request a review.

See how the technology works

What do you get?

A decision, a plan and a place to keep building.

  • A reasoned verdict and the main risks
  • A concrete plan you carry out in your own tools
  • One place for the idea, the analysis and the execution
  • Working on an idea or product together with others

What does Forenta add?

From idea to end product, compared with prompting alone.

Building straight from prompts in Claude Code, Cursor or Codex is fast and flexible. Forenta does not replace that. It adds structure, an independent review and a workspace around it, so you do not spend weeks building the wrong thing: the wrong assumption, the wrong scope or a product nobody is waiting for.

Prompting alone compared with Forenta
What you needPrompting aloneWith Forenta
Quickly build something that works
Structure and scope before you build
An independent review from several angles
Risks, assumptions and security made explicit
A concrete execution plan to build from
Build instructions per product type
Projects and history kept in one place
Work on an idea together

Check: available. Clock: in development. Cross: not by default.

You rarely build alone.

An idea gets stronger with more eyes on it. In a workspace you work on an idea or product together, with chat, tasks, decisions and documents in one place. In Forenta Enterprise you work together within roles, permissions and an audit trail, so you can always check who decided what.

Start with what you have.

An idea, copy or relevant code context is enough for a first assessment. Forge reads only what you provide.