Lattice vs Manual Setup: What Gets Automated
Lattice prepares a reviewable starting point for software projects, existing repositories, and self-hosted agents. It does not remove your responsibility for credentials, permissions, testing, security review, or production operation.
Manual Setup
- Research and record stack decisions
- Write project and agent instructions
- Configure linting, testing, and CI
- Create or adapt runtime-specific files
- Track compatibility and verify the result
With Lattice
- Collects the decisions in a structured workflow
- Generates reviewable files for the selected product
- Provides a setup or install path for supported output
- Reports verification and failure stages explicitly
Choose the Right Lattice Product
Lattice Project Builder (Paid)
Best when starting from scratch. Generates PROJECT_GUIDE.md, architecture plan, compatible stack, guardrails, CI/CD, and a feature-to-release handoff contract.
Agent Setup Builder ($29 once)
Best when setting up OpenClaw or Hermes Agent. Creates one personalized runtime setup and a guided installer.
Lattice Core (Free)
Best for existing codebases. Adds version-aware agent rules, AGENTS.md, provider instructions, verification commands, and drift visibility in one command.
Frequently Asked Questions
What is the difference between Lattice Project Builder and Lattice Core?
Lattice Project Builder is for new projects and generates your plan, stack, setup command, and multi-agent release workflow. Lattice Core is the free CLI for existing projects and adds version-aware guardrails, shared agent instructions, and verification workflows.
Does Lattice work for mobile apps too?
Yes. Lattice supports web, API, and mobile-oriented stacks including Expo.
Do I still keep control over the generated files?
Yes. Lattice generates files in your project and you can edit everything directly, including AI rule files and config.
Where does Agent Setup Builder fit?
Agent Setup Builder is a separate $29 one-time product for a personalized OpenClaw or Hermes Agent setup. It generates runtime-specific files and a guided installer, while provider and channel credentials stay in the official runtime setup.