Skip to content

Roadmap

Directions, not launch promises.

Our roadmap covers applications and the shared API behind them. These are product directions, not release dates or uptime reports. Readiness labels are separate from engine status and customer access.

Six current directions

One foundation, different kinds of work.

  1. 01

    AccelMars Team

    Your own team of AI colleagues.

    We are building a team that gets to know your work, thinks things through with you and helps carry it forward—without making you manage the machinery behind it.
    In development
  2. 02

    AccelMars Business

    Keep your company’s work moving.

    AccelMars Business is being built to help you operate a company: keep commitments, resources and obligations in view, carry work forward, and bring decisions to the right people.
    Planned customer product
  3. 03

    AccelMars Work

    From an intention to work you can steer.

    Organise, run and oversee an undertaking—from the first plan to results you can check and accept.
    Planned customer product
  4. 04

    AccelMars Ready

    Understand your progress. Be ready to explain it.

    Discover what your work amounts to, notice what needs preparation, and explain it with supporting records when it matters—not only when someone asks.
    Planned customer product
  5. 05

    AccelMars Run

    Keep the tools, services and resources behind your work running well.

    Run is designed to help you and your AI colleagues understand what supports your work, notice what needs attention and carry the right response through to a checked result.
    Planned customer product
  6. 06

    Freeport

    A living world of fictional companies

    Freeport is intended as a persistent world of fictional companies run by AI people, with history and work between those companies.
    Environment and showcase direction

Shared API · in development

The foundation is for builders, too.

Alongside our applications, we are developing api.accelmars.com as a way for software to request defined actions and inspect their results. App workflows help us identify the contracts builders need; an internal capability is not automatically a public endpoint.

Published API contracts, access terms and verified behavior determine what developers can use. Buying API usage does not by itself include every application.

Explore the API

Technical depth

Engine status is a separate question.

The engines and OS pages retain technical detail about the foundation underneath these product directions. A live engine does not make a product live, and a product plan does not change an engine's status.

Explore engines