ArchLog
ArchLog preserves the reasoning behind engineering changes by connecting code, documentation, incidents, and team conversations into a searchable engineering memory. It turns commits, pull requests, repository history, and connected collaboration sources into structured Decision Ledger entries and source-backed answers to questions about why systems were built as they were.
At a Glance
- Modern engineering organizations
- Growing engineering teams
- Organizations needing procurement, security review, or larger-scale deployment
AI Tools by ArchLog
(1)ArchLog
Engineering Decision History Tracker
Discussions
No discussions yet
Be the first to start a discussion about ArchLog
Products & Services
A structured, searchable record of engineering decisions extracted from commits, pull requests, discussions, documents, and repository history. Entries include the decision, reason, impact, risk/confidence, provenance, authors, affected files, and linked evidence.
Source-backed answers to questions about why a system or change is the way it is, drawing on decisions, files, commits, documents, and connected workspace sources.
Market Position
ArchLog positions itself as an engineering decision-history and institutional-memory layer rather than a conventional stale documentation page: it derives context directly from repositories and connected engineering tools, preserves chronology and reversals, and provides source-backed answers with visible provenance and confidence.
Leadership
Founders
Sahajpreet Kaur
Founder & CEO of ArchLog.
Kartik Yadav
Co-founder & CTO of ArchLog.
Executive Team
Sahajpreet Kaur
Founder & CEO
Founder and chief executive of ArchLog.
Kartik Yadav
Co-founder & CTO
Co-founder and chief technology officer of ArchLog.
Founding Story
ArchLog was started around the problem that engineering teams preserve what changed in version control but often lose why a decision made sense, what alternatives were considered, and what evidence supported it. Its initial vision is to keep that reasoning attached to code and organizational history so it survives team turnover and system evolution.
Business Model
Revenue Model
Subscription SaaS priced per company workspace and plan capacity rather than per seat on the Growth plan; paid plans provide defined limits for team members, repositories, connected sources, and AI requests. Enterprise pricing is sales-led.
Pricing Tiers
Up to 10 team members, 25 repositories, GitHub/Slack/Notion/Linear, 2,000 AI requests per month, Decision Ledger/provenance/team memory, 35 days, and no card required.
35-day free trial; up to 25 team members in one workspace, 100 repositories, GitHub/Slack/Notion/Linear, 10,000 AI requests per month, Decision Ledger/provenance/organizational memory, and priority support.
For procurement, security review, or scale requirements; organization requirements, terms, invoicing, and security-review needs are discussed with sales.
Target Markets
- Modern engineering organizations
- Growing engineering teams
- Organizations needing procurement, security review, or larger-scale deployment
- Recovering the rationale behind architecture, migration, authentication, retry, and incident-response decisions.
- Onboarding engineers and transferring context when an engineer leaves.
- Investigating incidents and tracing the evolution of a system across commits, pull requests, documents, and discussions.
- Searching a codebase and its engineering history for source-backed explanations.
- Preserving institutional memory for modern engineering organizations.
- The public homepage demonstrates the product with an illustrative simulated workspace called Acme Payments; it explicitly states the data is simulated and no real accounts are connected.