AI-Native ERP Evaluation · Operations-focused platform
Keel
The modern ERP for fast-moving teams
- Headquarters
- London
- Founded
- 2022
- Total funding
- ~$6M
- Valuation
- Not disclosed
Latest round: £5.5M Seed (Oct 2024, Firstminute Capital, Earlybird). Investors: Firstminute Capital, Earlybird.
By Glenn Hopper · Updated October 2026 · Vendor facts from vendor materials and public reporting as of March 2026. Confirm each claim in the demo.
Positioning
What Keel is built for
Takes the most radical approach in the group: a no-code platform to build custom operational software. Rather than offering fixed ERP modules, Keel lets an ops team member define custom data models and create workflows (tasks, approvals, forms) to manage them. It is open-source and API-centric. Targets companies where off-the-shelf ERPs don't fit their unique processes and who can't secure engineering resources to build internal tools.
AI capabilities
How Keel uses AI in accounting and reporting
- Intelligent, exception-based processes that flag anomalies and automate routine steps
- AI-assisted workflow generation from business requirements
- Custom data model creation (define your own entities and fields, no fixed schema)
- Software dev best practices including version control and sandbox testing for ops-built apps
- Open-source platform allows community extensions and full transparency
Compliance and audit readiness
Keel on controls, SOX, and the audit trail
Ops-focused, less about GAAP compliance. Keel acknowledges traditional ERPs were about boardroom compliance and quarter-end rollups, while Keel is about daily operations. Platform offers audit logs and a Trust Centre for security/privacy compliance. But for financial audit, if functionality is built on Keel by your ops team, auditors will treat it as an internally developed system requiring thorough documentation. Open-source codebase allows transparency.
SOX readiness in the comparison matrix: Build your own.
Migration and implementation
Moving to Keel: migration claims and go-live
Launch in weeks. An ops team member (no-code savvy) can build and deploy a production-grade system in a few weeks. Example: at HIVED (logistics startup), one ops person built a driver scheduling system on Keel quickly. Sequential adoption model means you don't switch everything at once. No consultants needed.
Migration speed in the comparison matrix: Weeks (no-code).
Integrations
Keel integrations: banks, billing, CRM, and payroll
Integration is everything-you-use, expected to keep existing tools and work alongside them. Provides connector APIs to pull and push data from Shopify, order systems, Zendesk, Xero, and whatever ops teams need. Open-source and API-first means developers can build custom integrations freely.
Who it fits
Which finance teams Keel fits
Growing tech-enabled businesses ($1M-$50M revenue) in regulated or novel industries wanting total flexibility and quick iteration. Ops and Biz Ops teams that need custom tooling without engineering resources. Companies where standard ERP modules simply don't fit.
Ideal stage in the comparison matrix: Early-stage / Ops teams.
Side by side
Keel against the other six
| Company | Approach | Total funding | SOX ready? | Migration speed | Ideal stage | Integrations |
|---|---|---|---|---|---|---|
| DualEntry | Full-Stack | >$100M | Yes (Ultra tier) | 24hr data + ~4 weeks | Mid-market | 13,000+ |
| Campfire | Full-Stack | $100M | In progress | Weeks (no consultants) | Growth / Pre-IPO | Growing |
| Rillet | Full-Stack | >$100M | In progress | 4 weeks (3 days fastest) | Startups / Mid-market | 200+ |
| Nominal | Augmentation | ~$30M | Preserves existing | Weeks (no migration) | Mid-market / Enterprise | Major ERPs + banks |
| Doss | Ops-Focused | ~$20M | Not yet | 2 weeks (fastest) | Product / Manufacturing | ~30 |
| Lensing | Full-Stack | $140M | Designed for it | <6 weeks for NetSuite | Late-stage / Pre-IPO | API-first |
| Keel | Ops-Focused | ~$6M | Build your own | Weeks (no-code) | Early-stage / Ops teams | API-first / Open |
Full scoring, the incumbent comparison, and the compliance reality check are in the AI-Native ERP Landscape.
Due diligence
Questions to ask Keel in a demo
The same ten questions apply to every vendor in the landscape. Make Keel answer them live, in the system, on your data where possible.
Q1
Show me the audit trail for an AI-generated journal entry.
If the AI auto-posts entries, your auditors will want to see exactly what triggered it, what data it used, and how it arrived at the amount. A clean audit trail is non-negotiable for SOX environments.
Q2
What happens to my data if your company shuts down next year?
These are venture-backed startups. Some will not survive. You need to understand data portability, escrow arrangements, and export formats before you sign.
Q3
Can I run your system in parallel with my existing GL for 90 days?
Parallel running is the gold standard for ERP migration. Any vendor that resists this request is optimizing for their sales cycle over your risk management.
Q4
Which Big 4 or national audit firm has signed off on your controls?
SOC 2 Type II is the minimum. But what you really want to know is whether a major audit firm has actually examined the system in a client engagement. Ask for the reference.
Q5
Walk me through a multi-entity consolidation with intercompany eliminations.
This is where simple demos break down. Real-world consolidations involve currency translation, minority interests, and elimination entries. Make them show it live, not in slides.
Q6
What does '24-hour migration' actually include?
Data migration is one piece. What about chart of accounts mapping, historical reporting continuity, user training, parallel testing, and auditor sign-off? Decompose the timeline into its real components.
Q7
How do your AI models handle edge cases and exceptions?
AI that works 95% of the time still means 5% of transactions need human review. Understand the exception workflow, how exceptions are flagged, and what the override process looks like.
Q8
Show me your permissions model for a SOX-compliant environment.
Segregation of duties, approval workflows, period locks, role-based access. These are not optional for public companies or companies preparing for an IPO. Ask to see the actual configuration, not a feature list.
Q9
What integrations are native versus built on Zapier or generic APIs?
13,000 integrations sounds impressive until you learn 12,900 of them are through a third-party connector platform. Native integrations are real-time and reliable. Generic ones break.
Q10
Can I speak with a CFO at a company your size who has been live for 6+ months?
The most important reference is a company at a similar stage to yours that has been through at least one full audit cycle on the new platform. Accept nothing less.
Ask SAL