How it works

Focused tools that cooperate on your machine.

A suite gets big because every feature has to live inside one binary. These stay small because they hand work to each other over local interfaces — so 1FileTool can stay a file tool and still know what your company decided last March.

  • Local-first
  • Bring your own AI
  • Human approval for consequential actions

The company workflow

Six things a company has to do. Twelve tools that do them.

Every product exists because one of these six stages was being done by hand, badly, at eleven at night. Pick a stage to see which tools cover it.

What am I actually making?

You describe the thing you want to exist. 1FounderTool turns that into a plan you can argue with, and 1AIVault keeps the reasoning so you are not re-deciding it in three weeks.

  • 1FounderToolIn design

    Describe the product. Get a plan, then a working build.

    Build and think
  • 1AIVaultAvailable

    Keep what your AI tools learn about your company.

    Build and think

The shared foundation

Focused alone. More powerful together.

Every product owns one discipline and refuses the rest. Four capabilities run underneath all of them, which is how they cooperate without any of them turning into a suite.

  • Memory

    Owned by 1AIVault

    Decisions, preferences and company knowledge, stored once and readable by every other app through MCP.

    Read by1DevTool, 1FounderTool, 1FileTool, 1MarketingTool, 1AudioTool
  • Execution

    Owned by 1VMTool

    A disposable machine to run something risky in. Agents get a sandbox; you get a snapshot to roll back to.

    Read by1DevTool, 1FounderTool, 1VideoTool
  • Voice

    Owned by 1AudioTool · In design

    Dictation in, transcription and spoken summaries out — so a long day of work can be handled without a keyboard.

    Read by1ShowcaseTool, 1VideoTool
  • Agents

    Owned by 1DevTool

    Routing, approval and session state for every coding agent you run, so a task survives being closed and reopened.

    Read by1FounderTool, Server Compass

A product only reaches for a layer when it needs one. 1FileTool does not need agents to compress a PDF, and it does not load them.

One request, five products

What “working together” actually means.

Ask for something that crosses four disciplines and watch which tool picks up each part. Nothing is uploaded between them — they hand off through the shared layers on your own machine.

Review yesterday’s customer feedback, remember the complaints that keep coming back, update the product plan, draft the response, and read me the summary.

  1. 1

    Review

    An agent pulls yesterday’s feedback and groups it.

    1DevToolvia agents
  2. 2

    Remember

    Recurring complaints are matched against what the vault already knows.

    1AIVaultvia memory
  3. 3

    Update

    The plan is edited in the project, not in a separate tracker.

    1DevTool
  4. 4

    Draft

    The public response is written against the same research.

    1MarketingTool
  5. 5

    Read back

    The summary comes back as audio. This step ships when 1AudioTool does.

    1AudioToolvia voice

The rules

Four commitments that shape every product.

These are constraints, not marketing. They rule out features people ask for, and they are the reason the apps look the way they do.

  1. Local-first wherever it is technically possible

    Files, keyword data, recordings, vault entries and virtual machines stay on your disk. When something genuinely has to leave — a model call you asked for, a deployment to your own server — the app says so before it happens.

  2. You bring the AI

    Every app takes your Claude, OpenAI, Gemini or Kimi key, or points at a local model through 1LocalAITool. We do not resell tokens and we do not have a model of our own to push you towards.

  3. Consequential actions wait for a human

    Agents can read widely and write freely inside a sandbox. Deleting, deploying, publishing and spending require you to say yes — and the app shows what it is about to do first.

  4. The apps talk through your machine, not our servers

    Cooperation happens over MCP and the local filesystem. There is no StoicSoft account tying the products together, because there is no StoicSoft server in the middle to hold one.

Questions

The four things people ask first.

Do I need all twelve products?
No. Every product works alone and most people start with one. The shared layers are opportunistic: if 1AIVault is installed, other apps can read your vault; if it is not, they carry on without it.
Does StoicSoft see my data or my prompts?
No. The apps run on your machine and call the AI provider you configured directly. There is no StoicSoft account and no server in the middle to log anything.
What does "bring your own AI" cost me?
Whatever your provider charges, billed by them, not us. You can also run local models through 1LocalAITool and pay nothing per token at the cost of slower answers.
How do the apps actually share memory?
1AIVault exposes a local MCP server. Other apps — and any coding agent you run — query it for decisions, preferences and company knowledge instead of asking you to re-explain the project.

One person can build a company.Their software should help them run it.

Free tiers on most apps. Seven-day refund on every paid one. No account needed to try anything.