Coming soon. This page describes the ShipForge AI architecture being built. The gateway boundary (auth, quotas, rate limits, model routing) is live; providers are not enabled yet.
Technology · Coming soon

How ShipForge AI works.

For customers who want to see under the hood. You don't need any of this to use ShipForge — but if you're curious, here's the architecture.

The short version.

Your app comes in. An evidence-backed launch plan comes out. Deterministic scanners and AI coordinate the analysis; automated quality gates check the findings before they reach you.

YOUR APP
SHIPFORGE AI
ANALYZE
FIX
VERIFY
LAUNCH READY
Model routing

You don't choose a model. ShipForge does.

ShipForge uses a model-routing layer that selects approved providers based on quality, cost, latency, modality, and availability. New providers are added when they win against existing ones — customers don't feel any of it.

Quality

We benchmark every candidate model against our own tasks — code, audit, planning, creative. Only winners are promoted.

Cost

Routine work runs on cheaper models. Serious work uses the top of the class. You don't pay for what your task doesn't need.

Latency

Interactive tasks favor faster models. Deep audits favor slower, more capable ones.

Modality

Images, video, vision and long-context work each route to specialists.

Availability

If a provider degrades, ShipForge falls back to another. No dead ends.

Providers today

The current lineup.

This list changes. New models get promoted whenever they win a benchmark. We publish the current lineup so you know what's approved to run against your project.

OpenAI

Primary Brain / Orchestrator

CTO / team leader

  • Understand the customer's project
  • Decide what needs to happen next
  • Architecture & complex debugging
  • Launch Doctor reasoning
  • Security reasoning
  • Coordinate specialists & compose the final response

Reserved for serious work. Not every cheap task should hit the strongest reasoning model.

Google Gemini

Fast, Multimodal, Cost-Efficient Worker

Fast analyst

  • Screenshots & UI understanding
  • Large project / file context
  • Document analysis & summaries
  • Routine classification & repetitive checks
  • Inexpensive high-volume processing
  • Vision tasks

The router picks the best cost/performance Gemini variant per task — never a hard-coded model.

Alibaba Qwen3-Coder

Code Specialist

Senior coding engineer

  • Flutter repository analysis
  • Code generation & refactoring
  • Tests & migrations
  • Dependency changes
  • Fixing errors
  • Agentic coding tasks with tools

Purpose-built for repository-level coding, tool use, and long-horizon agent workflows.

Zhipu GLM-5

Engineering Challenger / Backup

Second senior engineer

  • Independent engineering opinion when the primary is uncertain
  • Particularly complicated architecture
  • Difficult code issues that aren't resolving
  • Second technical review inside Launch Doctor
  • Provider-diversity failover when OpenAI is degraded

Deliberately not used on every task. Engaged when a second opinion or a fallback is genuinely warranted.

Z-Image-Turbo (6B)

Creative / Image Specialist

Visual designer

  • App Store & Google Play visuals
  • Onboarding artwork
  • Promotional & social launch images
  • Landing-page assets
  • Ad concepts
  • Product graphics with clean bilingual text

Fast, photorealistic, strong instruction adherence — tuned for the Launch Studio asset workflow.

Wan 2.7

Video Specialist

Motion designer

  • App Store & Google Play promo clips
  • TikTok / Reels / Shorts launch videos
  • Screenshot-to-video animations
  • Product teasers & feature demos
  • Image-to-video from generated app artwork
  • 9:16 vertical launch content

Text-to-video and image-to-video, 720p/1080p, 2–15 s clips, synchronized audio, multi-shot generation. One video engine at launch — Veo can be added later only if it wins a benchmark.

We don't rank providers on this page ("A beats B") because model performance changes constantly. What matters is that ShipForge always routes to the current best available option for the task.

Deterministic verification

Not everything should be an AI opinion.

For the things that are objectively right or wrong — exposed secrets, missing account deletion, disabled Row Level Security — ShipForge runs real code, not an AI opinion.

  • .env or secrets exposed in the repository
  • API keys embedded inside the Flutter app binary
  • RevenueCat restore-purchases function missing
  • Supabase Row Level Security disabled on user tables
  • Account deletion flow absent (required by App Store)
  • Crash monitoring not wired (Sentry / Crashlytics)
  • Outdated or vulnerable dependency versions
  • Privacy policy URL missing or broken
  • Android permissions not documented in manifest rationale
  • Apple usage-description strings missing for requested permissions
Quality Judge · Planned

Important work gets independently checked.

For high-stakes work — security, database changes, payments, App Store compliance, production architecture — ShipForge is designed to run an additional cross-check before the answer reaches you. This automated judge is a planned capability; during Founding Beta, high-stakes findings are checked by an independent model challenge and automated quality gates instead.

Triggers

  • Security review
  • Database changes
  • Payments & subscriptions
  • App Store compliance
  • Production architecture decisions

Pipeline

  1. 1

    Deterministic Scanner

    Finds facts (missing RLS, exposed keys, absent deletion flow, etc.)

  2. 2

    Primary AI

    OpenAI Architect reasons about impact and drafts the fix.

  3. 3

    Second Provider (when warranted)

    GLM-5 provides an independent engineering opinion.

  4. 4

    Quality Judge

    Cross-checks scanner facts against the AI proposal before it reaches the user.

Privacy

Your code stays yours.

Provider requests are made through ShipForge — with your project scoped, your data minimized, and no training on your code. Restricting routing to specific providers is a planned capability.

No training

Your code is never used to train any model. Provider requests are made with training disabled where the provider supports it.

Provider allowlist

Restricting routing to a chosen subset of providers — for example, US-only or EU-only — is a planned capability.

Server-side keys

Your keys never touch the client. ShipForge's own provider keys are managed server-side and are never exposed.

Enough architecture. Try it on your app.

You'll never touch any of this. It just works.

Run Free Launch Score