Akashic
Subscribe Open WorkspaceWorkspace

Private beta opens soon. Subscribe for Akashic product updates.

℗ 2026 Colossal Capital · managed SaaS

Any repo becomes a Collection.
Built for teams and every AI-built codebase.

Connect any Git repository — legacy monolith, greenfield service, Cursor project, Claude Fable, ChatGPT canvas, or Gemini app. Each repo is a Collection. Bundle Collections into a Library or Workspace, and iterate toward a shippable product — engineers, product, and identity-provisioned AI agents in one portal.

One-shot AI builds aren't every repo. Claude Fables, ChatGPT projects, and Gemini spikes are the urgent case — sprawling sessions that work once but need a path to iteration. Akashic is built for that moment and for every other codebase you already have.

Open Workspace Repo → Collection → Ship

collection · library · workspace · human at the gate

AI-built repos · the timing

One-shot masterpieces need a label, not a landfill

Teams generate complete apps in single sessions. Akashic turns those spikes into maintained products.

What a one-shot build is

A Claude Fable, ChatGPT project, Gemini app, or similar one-shot AI build — a repo born from a single creative session. It runs, it impresses, and then it sits there because nobody knows what to do with it next.

What a Collection is

Any repository you connect — AI-built or not — becomes a Collection: analyzed, ticketed, and improved with a human at the gate.

What a Collection holds

Code, context, tickets, and docs — together

A Collection is the repo plus everything it takes to keep shipping: the code agents run against, how it was built, the tickets your team shares, and the docs they read.

Code

What agents run against

The connected repository — indexed so analysis, search, and agents work from the real tree, not a guess.

RepoSource, branches, and history
AnalysisGaps become tickets in an order a team can ship
SearchAnswers cite files, not model memory
Context

How it was made

Prompt history and playbooks stay with the Collection, so the next session starts where the last one left off.

PromptsHow the repo was actually built
PlaybooksConventions agents inherit
ReviewA human at the moments that matter
Tickets

Work the team can see

Analysis lands as tickets. Product and eng share one gate before anything syncs to your board.

BoardsLinear, Jira, GitHub Issues — after the gate
DedupeSame work is not filed twice
ApprovalPeople stay the approver
Docs

What the team reads

Documentation stays current as the Collection changes — the same Workspace engineers and product already use.

GuidesProduct and operator docs in one place
CoverageSee what is still missing
HistoryVersioned with the Collection

One-shot AI builds arrive heavy on prompts. Mature repos arrive heavy on tickets and docs. Same Collection, different balance.

Product structure

From repo to shippable product

Connect repos, bundle Collections, compose the Product Board, ship.

01 · REPO

Collection

Connect any Git repo. Analysis finds gaps, files tickets, and agents work them — with human approval at the gate.

One Collection per repo.
02 · BUNDLE

Library or Workspace

Add Collections to a Library (same entity — API, web, contracts, infra) or a Workspace (cross-entity — org, client, portfolio). Shared history and one approval gate.

The album — or the full roster in one room.
03 · COMPOSE

Product Board

Drag Collections into role slots — frontend, API, data, infra, docs — until the bundle is a shippable product.

Compose in the Workspace.
04 · SHIP

Reconcile & deploy

Tickets across the bundle, agent workflows, human approval, then ship under scoped identities.

Product and eng share the gate; agents run the work.

Workspace is where your team works Collections, composes the Product Board, reconciles tickets, and ships together. Web portal, desktop app, or VS Code — same Library, same board, same gate.

Product Board

Slot Collections into a shippable product

Open the Product Board on any Library or Workspace — analysis runs against the bundle; tickets file across repos.

Drag-and-drop composition

Each slot is a role in the product. One Collection per slot — clear ownership per lane.

App or infrastructure

Switch the board to emphasize product roles or the rails underneath — without mixing the two.

Ship from the bundle

Tickets and agent work run against the composed board — not a loose bag of repos.

The Product Board lives in the Workspace — libraries and workspaces share the same composition surface.

Libraries

Multiple repos, one entity, one Library

Fables especially rarely stay in one repo — but neither do most real products. Group every related Collection into a Library, compose slots on the Product Board, and run analysis, tickets, and agents across the full stack.

collection/payments-apiindexed
collection/payments-webindexed
collection/shared-contractssyncing
collection/deploy-confignew

library · payments · 4 collections

Cross-collection view

See how Collections in the Library relate — before anyone merges.

Unified reconciliation

Tickets dedupe against Linear, Jira, and GitHub Issues across the whole Library. One gate.

Library-scoped agents

Agents per Collection with shared Library context — the whole album, not one track.

Collaborate · your Workspace

One place for eng, product, and agents

Akashic is a collaborative product — web portal, desktop app, and VS Code extension all sharing the same Workspace. Engineers run analyses and review agent PRs; product approves at the reconciliation gate — whether the Collection started as a Fable or shipped years ago.

Web portal

Analyses, chat with citations, ticket queue, agent approvals — no install.

Open your Workspace →

Desktop app

Run Akashic locally with a bundled local model — private and offline-capable by default. Switch to your own keys anytime; same Workspace, same gate.

Download the app →

VS Code extension

Connect Collections, run analysis, search with citations — same Workspace as the portal, from your editor.

VS Code Marketplace →

Chat with citations

Answers from indexed Collections — file paths, not model memory.

Playbooks

Conventions from each Collection, stored in your Workspace.

Managed CI/CD

Builds, scans, and deploys — routed to your targets.

Human-in-the-loop queue

Approvals for syncs and deployments — policies you control.

Codebase, PM & documentation integrations

Connect where your code lives, where your team tracks work, and where your docs live. OAuth through Idio — credentials stay in your vault; Akashic reads boards and docs for context and writes reconciled tickets back after the gate. Planned hosts are on the roadmap.

Code hosts

GitHub
GitLab
Bitbucket

PM tools

Jira
Linear
Asana
Monday.com
ClickUp
GitHub Issues
Bitbucket IssuesPlanned
Azure DevOpsPlanned
Google SheetsPlanned
Microsoft PlannerPlanned
Microsoft ListsPlanned

Documentation

Confluence
Notion
Linear
Monday.com
ClickUp
GitHub WikiPlanned
Google DocsPlanned
SharePointPlanned

How work gets done

Agents execute. People approve.

Tickets that span the stack become ordered work for named agents, gated by a human where it matters. Every run is auditable; tickets, plans, and decisions stay in one Workspace.

Code

The connected repo agents run against.

repocontext

Context

Prompts and playbooks — how it was made.

gatereview

Gate

Human approval before tickets sync or code merges.

Ship

Docs, tickets, and the product you actually release.

Code the repo Context prompts · playbooks Gate human approval Ship tickets · docs Agents named identities

Named identities

Specialists with their own names

Named specialists with their own identities — planning, code, review, security, release, and operations. ie, the platform helper, guides the flow.

ObVect runs the workflows underneath. Bring your own models. See ObVect →

ie

Akashic — portal helper.

Guides onboarding and the other agents.

Platform agents — no first among equals.

◎

Nomkhubulwane

Zulu — Princess of the Sky.

Plans and roadmaps. Read-only on code.

☀

Olorun

Yoruba — owner of the sky.

Composes Product Boards. Read-only on code.

☽

Dyaus

Vedic — sky father of the open heaven.

Analysis, exploration, and product browsing. Read-only.

🕉

Shiva

Hindu — Lord of transformation.

Restructures the repo and consolidates docs before implementation begins.

⚡

Zeus

Greek — Olympian sky king.

Cloud and production deploys.

☀

Amaterasu

Shinto — celestial sun sovereign.

Frontend.

🫧

Aphrodite

Greek — goddess of creation and connection.

Backend and APIs.

⚒

Sunan Ambu

Sundanese — the noble mother, dweller of kahyangan.

Creates and tends the tools agents use.

📦

Waaq

Oromo — sky creator.

Releases, packages, and images.

⌂

Nyame

Akan — sky vault.

Data, schemas, and storage.

☘

Lugh

Celtic Irish — master of all crafts.

General code edits and PRs.

◉

Ra

Egyptian — sun who sees all.

Code review. No writes.

天

Shangdi

Chinese — Mandate of Heaven.

Security and compliance.

⬡

Heimdall

Norse — watchman of the sky-bridge.

Tests and coverage.

✎

Dewi Saraswati

Indonesian / Balinese — goddess of knowledge and flow.

Creates and syncs tickets across your boards.

✧

Ahura Mazda

Zoroastrian — Wise Lord of high heaven.

Docs and reports.

🌊

Poseidon

Greek — Earth-Shaker.

CI and pipelines.

☿

Mercury

Roman — swift messenger.

Edge performance.

☷

Pachamama

Andean — earth mother who holds what is built.

Deploy health and SLOs.

▣

Perun

Slavic — thunderer.

Alerts on breakage.

◇

Thought Woman

Pueblo / Tse Che Nako — she thinks the world into being.

Architecture map.

〜

Quetzalcoatl

Aztec — feathered serpent of wind.

Playbooks only — never opens code PRs.

✦

Kāne

Hawaiian — giver of life.

Private model training.

𒀭

Anu

Mesopotamian — highest heaven.

Boundary and access policy.

♛

Ishtar

Mesopotamian — queen of heaven.

Analytics and restore points.

☁

Tengri

Turkic — Eternal Blue Sky.

Logging.

⛈

Ukko

Finnish — sky thunderer.

Workflows.

🚪

Janus

Roman — two-faced gatekeeper.

Ticket reconciliation.

⚖

Maat

Egyptian — feather of truth.

UX simulation.

Governance · compliance

Every agent action — attributed, gated, and exportable

Autonomous, never unaccountable. Agents commit under their own provisioned identity, every action lands in a tenant-scoped audit trail, and the moments that matter are human-gated. Built for SOC 2 and GDPR.

Per-agent commit identity

Each commit, push, and PR is authored by that agent — clean Git blame, not an anonymous shared bot.

Full audit trail

Every agent action is recorded per tenant, filterable in the portal, and exportable on request.

Approval gates where they count

Release a ticket to an agent, approve a PR before merge, and sign off a production deploy — each optional per environment.

Off-portal notifications

Every gate notifies a human with a deep link, so approvals never stall in a queue nobody's watching.

Enterprise auth

MFA, SSO, and user provisioning — through Idio.

GDPR-ready by default. The audit trail is downloadable and erasable on request — your data stays portable, and right-to-erasure is a button, not a support ticket. Observability and access policy are managed by ObVect →

Powered by ObVect

The engine behind the portal

Akashic is the product you use. ObVect is the AI backend underneath.

ObVect — the AI backend

Inference, retrieval, and agent runs — one API across the models you already use, grounded in your code and docs.

Gap analysis

Maps your repos, finds what's missing, and turns gaps into ordered tickets — with a human at the gate.

Private models

Opt in to a model trained from how your products actually evolve — not a dump of the source. More on ObVect →

Agent concurrency · by design

Unlimited configurations. Concurrent slots per tier.

Provision as many agents as you need — no per-person cap, no per-agent seat charge. Your Colossal Capital tier sets how many agents run at once. When slots are full, excess runs queue automatically and start when a running agent finishes. People stay the approver.

Teams & organizations

Business 50 concurrent · Business+ 100 · Org 250 · Org+ 500 · Enterprise unlimited. Excess queues. Human seats are priced separately on team plans — agents are not sold per seat.

Individuals

Free 3 concurrent · Pro 10 · Ultra 25. Same rule: unlimited configurations, queue when slots are full. Ultra and above include a priority queue.

Approver, not bystander. Agents execute under scoped identities; a human reviews and reconciles every change. Full concurrency & pricing →

Developed in Partnership with Ackward Roots Inc

Product newsletter

Updates on Akashic

Product news, rollout notes, and when beta access opens. Akashic itself is free — you pay for the ObVect tenant that runs your Workspace.

Product updates only. Unsubscribe anytime.