Navigate

Quick find

Navigate NeuroForge

Esc

Start typing to search public pages and evidence.

    First pilots / qualification open

    Apply intelligence to one problem that matters.

    Bring one real problem, one environment, and one person who owns the decision.

    NeuroForge is qualifying its first commercial, co-development, and research pilots. Success, failure, and stop conditions are agreed before work starts.

    CommercialCan technicians search approved maintenance records on the existing workstation?
    Co-developmentCan a second operator run one developed ERAIS workflow without founder intervention?
    ResearchDoes added stored capability improve a fixed quality gate without proportional active work?

    A good first pilot

    One owner. One environment. One result worth knowing.

    A good first pilot is small enough to control and important enough to change a decision—even when the answer is no.

    You bring

    The decision owner, lawful access, representative non-sensitive cases, target environment, and people who can witness the result.

    Before we start

    Rights, data handling, funding, roles, baseline, acceptance criteria, security, publication, and stop conditions close in writing.

    When we finish

    The owner sees the agreed cases, evidence, and failures—then chooses deploy, change, remediate, rescope, or stop.

    Three different commitments

    Choose the path that matches the question.

    Each path has its own start gate, deliverable, risk boundary, and evidence. Interest alone does not change a candidate's status.

    01 / available engagement

    Fit-test-led commercial pilot

    Start with the A$4,800 10-Day AI Fit Test. Ask whether one useful workflow fits the real machine, approved data, and operating limits.

    • Qualification can begin now
    • A stop or hardware-change decision is useful delivery
    • No product or SLA implication
    Compare available engagements
    02 / gated candidate

    Product co-development pilot

    Test one developed ERAIS surface in a partner environment—for example, whether a second operator can reproduce the workflow.

    • Discovery and gate design are open
    • Delivery waits for the candidate's entry gate
    • No general-availability claim
    Inspect candidate gates
    03 / funded protocol

    Research pilot

    Answer one falsifiable systems or model question under a frozen baseline, rights set, compute budget, and review path.

    • Partner roles are explicit
    • Null and negative outcomes remain valid
    • Publication requires separate approval
    Review the research offer

    Commercial pilot options

    Four commercial engagements can enter qualification now.

    The 10-Day AI Fit Test is the default first step. Every path ends with accept, remediate, extend, or stop—and a well-supported stop is useful.

    NF-A0Commercial stateAvailable — bounded service

    10-Day AI Fit Test

    What useful AI can run inside your actual data, hardware, connectivity, power, and accountability limits—and is deployment worth funding?

    For A$4,800 ex GST, inspect the real system boundary, run a small local demonstration, and leave with the evidence to deploy, change the model or hardware, remediate—or stop.

    Market-test price
    A$4,800 ex GST
    Duration
    Up to 10 business days
    Boundary
    Audit and local demonstration only. No production deployment, full-corpus ingestion, bespoke integration, continual learning, certification, penetration test, production SLA, or guarantee of accuracy, savings, deployability, or ERAIS performance.
    NF-ACommercial stateAvailable — bounded service

    Private AI Deployment Sprint

    Can one valuable AI workflow run usefully inside your approved local hardware and data boundary?

    Prove—or disprove—that one useful workflow can run locally, then leave with the tested system and the evidence behind the decision.

    Duration
    2–4 weeks
    Boundary
    No production high availability, public exposure, autonomous action, continuous learning, broad fine-tuning, certification, 24/7 support, or unbounded integration.
    NF-BCommercial stateAvailable — bounded service

    AI Evidence & Release Audit

    Can one AI release be reconstructed and defended technically?

    Reconstruct one AI release end to end—what it claims, what it used, what failed, what changed, and why the decision should be release, remediate, or hold.

    Duration
    2–4 weeks
    Boundary
    Technical evidence and release reconstruction only. No legal opinion or privacy, clinical, safety, cyber, engineering, or regulatory certification.
    NF-CCommercial stateAvailable when qualified

    Research & Benchmark Partnership

    What does one controlled experiment say about a material technical or commercial decision?

    Turn one important uncertainty into a pre-agreed experiment that a decision owner can act on and a reviewer can inspect.

    Duration
    6–12 weeks
    Boundary
    One question, one controlled protocol, one decision. No open-ended R&D programme, guaranteed positive result, or automatic product-performance claim.

    If the Fit Test passes

    Earn the next step. Keep an exit at every stage.

    Larger commitments follow customer-visible evidence. They are not assumed at the start.

    1. 01
      Audit + local demo

      Map the limits and show what works on the target machine.

    2. 02
      Staged local deployment

      Deliver one workflow using the best-fit qualified model and runtime.

    3. 03
      Operate + update

      Train the operator. Test every change. Keep restore and rollback available.

    4. 04
      Repeat + productise

      Earn repeat sites, support, reusable software, or licensing from real use.

    Gated co-development

    Three candidates can enter discovery. None enters delivery by default.

    NF-DCommercial stateGated design partner

    ERAIS Gateway

    Can one approved workload use a controlled local endpoint with the required operational controls?

    Duration
    6–10 weeks after gate
    Boundary
    One approved workload and supported configuration. No OpenAI-wide compatibility, general availability, production SLA, or customer-operability claim before the gate passes.
    NF-ECommercial stateGated design partner

    Training Workbench

    Can a second operator reproduce one bounded data-to-evidence workflow?

    Duration
    8–16 weeks after gate
    Boundary
    One registered data-to-evidence workflow, environment, operator cohort, model/profile, rights set, and acceptance protocol. Not a general training platform.
    NF-FCommercial stateGated design partner

    Evidence Control

    Can a repeated release-evidence process become a reviewer-operable workflow?

    Duration
    6–10 weeks after gate
    Boundary
    One repeated release-evidence process, one minimum schema, file or bounded API-export integration, and one second-reviewer workflow. Not a generic governance or accreditation platform.

    Bring one useful problem

    Tell us what must work, where it must work, and who decides.

    The first conversation confirms what may be tested and what would justify deployment, a change of direction, or a deliberate stop.

    Start the audit conversation