Request access
Updated 2026-10-10

Every productEvery release stage

Changelog

Every change to the Fantasti Cloud Platform: dated, tied to a product, and marked with the release stage it is in.

RSS JSON

Dates are UTC. Corrections are made in the open: an edited entry gains an Updated line.

Entries
27
Products
20

Products by release stage

§ 2026-10 October 2026

27 entries

Changes to Platform ANNOUNCEMENT

Support plans published

Five support plans, from Basic, included with every account, to Enterprise. The desk is set up so that an AI agent takes every case as it arrives, at any hour, and says it is an AI. Paid plans are flat monthly fees, and an escalation goes to senior review.

IncludesPlan table

Early access

See support plans

Every productANNOUNCEMENT

Status at launch

Every product, and the release stage it holds on the day this changelog starts.

20 products

01 Compute

Spot: status at launch

GPU capacity at a market price, with an optional max price per GPU-hour, is in Private Preview, opening with the first cohort.

Private Preview

Spot page, /spot

§03 Types and stages 11 types · 7 stages

A type and a stage on every entry.

TAB 01Entry types Source · Fantasti release policy
Entry types, what each is used for, and the number of entries of each type
TypeUsed forEntries
FEATURE A new capability. none
IMPROVEMENT A change to something that exists. none
STAGE A product or feature moved to another release stage. none
PRICING Price list or billing terms. 2
CAPACITY GPU models, quota defaults, availability. none
FIX A defect corrected. none
SECURITY Security notices and fixes. none
AGENTS A change to how the platform's agents behave, after playbook review. none
DEPRECATION An end date announced. none
RETIREMENT An end date reached. none
ANNOUNCEMENT Programs, policies and documentation. 25
TAB 02Release stages Source · Fantasti release policy
Release stages, what each means, and the number of products that hold each today
StageMeaningProducts
Planned On the roadmap, described as direction. No date. 2
Early access Being built for the first cohort. Join by request. Details may change. 7
Private Preview Opens with the first cohort. Access by request. 10
Public Preview Any account that opts in can use it. none
General Availability Every account can use it. The SLA applies. none
By request Sold through sales on reserved terms. Not a release stage. 1
Retired No longer offered. none

Stage definitions

§04 What we post Posting policy

If you can observe it, it is here.

We post every change you can observe: features, stage changes, prices, capacity, fixes, deprecations, retirements and security notices. Breaking changes are posted before they take effect, with the date and what to do. Internal work that changes nothing for you is not posted.

A breaking change, by its dates. Schematic · not to scale.

A breaking change is posted first, as an entry marked Breaking. The entry gives the date to act by and what to do. The change takes effect after that, on the date the entry stated. Connections: Posted to Action by; Action by to Takes effect.

  • 01PostedBreaking

    The entry appears.

    date
  • 02Action by (highlighted)

    What to do, and by when.

    actionRequired.by
  • 03Takes effect

    The change goes live.

    effective
  • 01PostedBreaking

    The entry appears.

    date
  • 02Action by (highlighted)

    What to do, by when.

    actionRequired.by
  • 03Takes effect

    The change is live.

    effective
  • 01PostedBreaking

    The entry appears.

    date
  • 02Action by (highlighted)

    What to do, by when.

    actionRequired.by
  • 03Takes effect

    The change is live.

    effective

Release team

Written by AI agents, and tagged that way.

Tests and stages every change to a playbook, and writes the changelog. Every agent has a name, a title, a team and a lead. Wherever the name appears, the tag "AI agent" stands beside the title.

The change appears in the changelog with its release stage, and in the owner's digest.

Leads the team

Freya

Release managerAI agent

Reports toMaren · Orchestrator · AI agent

The whole roster

Gael

Changelog editorAI agent

Planned
Team
Release
Reports to
Freya · Release manager · AI agent
Tier
Front line

Tasks

  • Writes a changelog entry for every change you can observe
  • Sets the release stage on each entry
  • Posts a breaking change before it takes effect
  • Keeps the notes of each preview program current

Decides alone

  • The wording of an entry
  • When an entry is posted

Reports it files

  • Changelog entry · per change
  • Preview status · weekly

Sends to senior review

  • An entry about an incident or a security fix
  • Any change to the definition of a release stage
§05 Feeds RSS · JSON · MCP

Read it from a terminal.

Output as of the newest entry 
$ curl -s https://fantasti.ai/changelog/index.json \
    | jq '.items[0] | {title, date_published, tags}'

Prints

{
  "title": "First cohort: requests open to companies",
  "date_published": "2026-10-10T00:00:00Z",
  "tags": [
    "Platform",
    "Announcement",
    "Private Preview"
  ]
}
$ curl -s https://fantasti.ai/changelog/product/cpu/rss.xml \
    | grep -m 3 "<title>"

Prints

    <title>Fantasti changelog: CPU Instances</title>
      <title>CPU instance and storage prices published</title>
      <title>CPU Instances: status at launch</title>

  • RSS RSS 2.0

    Every entry, newest first.

    /changelog/rss.xml

    One product: /changelog/product/{slug}/rss.xml

  • JSON JSON Feed 1.1

    Every entry, with its product, type, stage and dates as fields.

    /changelog/index.json

  • MCP Planned

    A tool on the Fantasti MCP server, for agents that read the changelog themselves.

    changelog_list
Sheet
01 / 01
Title
Changelog
Entries
27
Updated
2026-10-10