Docs
How the apps work.
These notes cover the product decisions already settled. Launch dates and pricing are still open.
From brief to result
Each app handles its own job. The steps stay visible before a run begins.
- Choose the app
- Start with the product that matches the work.
- Write the brief
- Describe the job and attach whatever the app needs.
- Check the steps
- Read the plan and change anything that looks wrong.
- Read the result
- The finished work stays beside a record of what changed.
What is being built
ZerofyAI is still pre-launch. Each app has its own site, account and roadmap.
- Our lineup
- Use Unicorn for idea validation, Capital for finance, Astral for analytics, Streak+ for retention and Lore for documentation.
- Separate products
- Subscriptions, billing and product data stay with the app you choose.
- What is still open
- Pricing and the launch date have not been set.
- Release updates
- The waitlist sends one email when the next release is ready.
Your first useful run
Pick one small job you already do by hand.
- 1. Pick an app
- Start with the problem already on your desk, then choose the app that owns it.
- 2. Describe one job
- Write one sentence about the smallest job you do by hand more than once a week.
- 3. Read the steps
- The steps appear before the run. Change anything that looks wrong.
- 4. Run it once
- Read the change report. If the job comes back, keep the workflow.
Workflows
A workflow belongs to the app where it was created.
- Describing
- Write the job in plain English. The app saves the brief beside the steps it creates.
- Editing
- Open any step to change its inputs or outputs. If you write code, you can edit the code too.
- Scheduling
- Add a schedule when the job should run without being asked.
- Versioning
- A new version changes future runs. Old runs keep the steps they actually used.
Runs and logs
A run is one attempt at a workflow, with a record of what happened.
- The record
- Inputs, steps, outputs and the final diff stay together.
- When a step fails
- The run stops where it broke. Earlier work stays put, and the log points to the input that failed.
- Retrying
- A retry starts at the failed step. The earlier work stays where it is.
- Spend
- Each run keeps its model usage, so costly work is easy to spot.
Model keys
Use a provider key you own, or use capacity offered inside that app.
- Your keys
- Add a provider key and runs use that account and its rate limits.
- Included capacity
- Availability may differ by app. Pricing is still being worked out.
- Mixing
- Choose per workflow inside the app. Different steps can use different providers.
- Training
- Customer prompts, runs and documents stay out of ZerofyAI model training. A provider’s own terms apply when you bring its key.
Export your data
The export plan starts in the app that created the work.
- Workflows
- Workflows will download as plain configuration you can read and keep in your own repository.
- Runs
- Run history will use newline JSON, with one object and one diff per run.
- Documents
- Lore will export documents as Markdown and keep the metadata with them.
- When
- Downloads will stay inside the app. No support request will be required.