Docs /roadmap/timeline

Development Timeline

Project timeline, milestones, and release schedule for Izri.

📋 Overview

This document outlines the development timeline with realistic estimates and key milestones.

Project Start: October 2025 (Initial Commit)

Current Phase: Phase 1 (Foundation) - ~50% Complete

Next Milestone: Complete repository analysis and AI service integration

🎯 Phase Timeline

Phase 1: Foundation (October 2025 - Q1 2026)

Duration: 12-16 weeks

Status: 🚧 In Progress (~50% complete)

Objectives:

  • ✅ Set up monorepo infrastructure
  • ✅ Implement authentication (GitHub OAuth)
  • ✅ Build core database schema
  • ✅ Create project management CRUD
  • ✅ Implement repository analysis
  • ✅ Build organization management
  • 📋 Complete API token system
  • 📋 Implement webhook infrastructure

Key Deliverables:

  • Monorepo with Turborepo
  • React Router v7 + Vite frontend
  • Hono + tRPC backend
  • PostgreSQL + Drizzle ORM
  • Better Auth integration
  • GitHub OAuth working
  • Project CRUD operations
  • Repository cloning and analysis
  • Organization management with RBAC
  • API token generation and management
  • Webhook delivery system

Milestone: Alpha Release (Internal Testing)

Phase 2: AI Test Generation (Q1 - Q2 2026)

Duration: 12-14 weeks

Status: 📋 Planned

Start Date: February 2026 (est.)

Objectives:

  • Integrate OpenAI/Anthropic APIs
  • Build prompt engineering system
  • Implement unit test generation
  • Implement integration test generation
  • Implement E2E test generation
  • Create test review and approval flow

Key Deliverables:

Week 1-3: AI Integration

  • OpenAI API client with error handling
  • Anthropic Claude alternative
  • Provider abstraction layer
  • Token usage tracking
  • Cost estimation

Week 4-6: Unit Test Generation

  • Function signature analysis
  • Edge case identification
  • Framework-specific test generation (Jest/Vitest)
  • Mock generation for dependencies
  • TypeScript type handling

Week 7-9: Integration Test Generation

  • API endpoint detection
  • Request/response schema analysis
  • Database interaction tests
  • tRPC procedure tests
  • Authentication flow tests

Week 10-14: E2E Test Generation

  • User flow analysis
  • Playwright test generation
  • Page object pattern
  • Form interaction tests
  • Visual regression tests

Milestone: Beta Release (Selected Users)

Phase 3: Test Execution (Q2 - Q3 2026)

Duration: 10-12 weeks

Status: 📋 Planned

Start Date: May 2026 (est.)

Objectives:

  • Build Docker-based test execution engine
  • Implement real-time test streaming
  • Create coverage reporting
  • Build comprehensive dashboards
  • Implement notification system

Key Deliverables:

Week 1-4: Test Runner

  • Docker container orchestration
  • Framework detection (Jest, Vitest, pytest)
  • Environment variable injection
  • Dependency installation
  • Parallel execution
  • Real-time log streaming

Week 5-7: Results & Coverage

  • Result collection and storage
  • Coverage analysis integration
  • Historical data tracking
  • Result comparison
  • Trend analysis

Week 8-10: Reporting

  • Test run dashboard
  • Coverage visualization
  • Flaky test detection
  • Performance metrics
  • Quality gates

Week 11-12: Notifications

  • Email notifications
  • Slack/Discord integration
  • Webhook system
  • Custom notification rules

Milestone: Public Beta Release

Phase 4: CI/CD & Advanced Features (Q3 - Q4 2026)

Duration: 10-12 weeks

Status: 📋 Planned

Start Date: August 2026 (est.)

Objectives:

  • Integrate with major CI/CD platforms
  • Implement advanced AI features
  • Add visual and accessibility testing
  • Optimize test execution
  • Scale infrastructure

Key Deliverables:

Week 1-3: CI/CD Integration

  • GitHub Actions integration
  • GitLab CI support
  • Status checks on PRs
  • Test summary comments
  • Quality gates

Week 4-6: Test Optimization

  • Test suite analysis
  • Redundant test detection
  • Smart test selection
  • Execution time optimization
  • Prioritization algorithms

Week 7-9: Advanced Testing

  • Visual regression testing
  • Accessibility testing (WCAG)
  • Performance testing
  • Cross-browser testing
  • Mobile browser testing

Week 10-12: Infrastructure

  • Horizontal scaling
  • Multi-region deployment
  • Performance optimization
  • Load testing
  • Monitoring & alerting

Milestone: v1.0 General Availability

Phase 5: Enterprise & Scaling (Q4 2026 - Q1 2027)

Duration: 10-12 weeks

Status: 📋 Planned

Start Date: November 2026 (est.)

Objectives:

  • Implement enterprise features
  • Add security and compliance
  • Support large-scale deployments
  • Create on-premises option
  • Build partner ecosystem

Key Deliverables:

Week 1-3: Enterprise Security

  • SSO integration (SAML, OAuth)
  • Advanced RBAC
  • Audit logging
  • IP allow-listing
  • Data encryption

Week 4-6: Compliance

  • SOC 2 Type II
  • GDPR compliance tools
  • Data residency options
  • Compliance reports
  • Data retention policies

Week 7-9: Scaling

  • Multi-tenancy optimization
  • Database sharding
  • Cache optimization
  • CDN integration
  • Rate limiting improvements

Week 10-12: On-Premises

  • Self-hosted package
  • Air-gapped deployment
  • Custom domain support
  • LDAP/AD integration
  • Enterprise documentation

Milestone: v1.5 Enterprise Ready

📅 Development Goals

Q4 2025 (Oct - Dec)

Focus: Complete Phase 1 Foundation

Goals:

  • Complete repository analysis (real implementation)
  • Implement AI service integration (real APIs)
  • Build API token system
  • Implement webhook infrastructure
  • Launch Alpha release

Metrics:

  • Repository analysis working end-to-end
  • AI service generating real tests
  • 10 alpha users onboarded
  • 50+ projects analyzed
  • 100+ tests generated

Q1 2026 (Jan - Mar)

Focus: Phase 2 AI Test Generation

Goals:

  • Integrate OpenAI/Anthropic APIs
  • Implement unit test generation
  • Implement integration test generation
  • Implement E2E test generation
  • Launch Beta release

Metrics:

  • 100 beta users
  • 500+ projects
  • 10,000+ tests generated
  • 1,000+ test runs executed

Q2 2026 (Apr - Jun)

Focus: Phase 3 Test Execution

Goals:

  • Build test execution engine
  • Implement coverage reporting
  • Create comprehensive dashboards
  • Implement notification system
  • Launch Public Beta

Metrics:

  • 1,000 users
  • 5,000+ projects
  • 100,000+ tests generated
  • 10,000+ test runs/week

Q3-Q4 2026

Focus: Phase 4 CI/CD Integration & Scaling

Goals:

  • GitHub Actions integration
  • Advanced AI features
  • Enterprise features
  • Launch v1.0 GA

Metrics:

  • 10,000 users
  • 1,000 paying customers
  • 50,000+ projects
  • 1,000,000+ tests generated
  • 99.9% uptime SLA

🎯 Key Milestones

Milestone 1: Alpha Release

Target: January 2026

Criteria:

  • ✅ Core authentication working
  • ✅ Project management complete
  • ✅ Repository analysis functional
  • API tokens implemented
  • Basic documentation complete
  • 10 alpha testers recruited

Deliverable: Invite-only access

Milestone 2: Beta Release

Target: April 2026

Criteria:

  • AI test generation working
  • Unit tests generated successfully
  • Integration tests working
  • E2E tests generated
  • Test review flow complete
  • 100 beta users recruited

Deliverable: Public beta signup

Milestone 3: Public Beta

Target: July 2026

Criteria:

  • Test execution engine stable
  • Coverage reporting working
  • Dashboards complete
  • CI/CD integrations working
  • Documentation comprehensive
  • Performance optimized

Deliverable: Open to public

Milestone 4: v1.0 GA

Target: October 2026

Criteria:

  • All Phase 1-4 features complete
  • Production-ready infrastructure
  • 99.9% uptime achieved
  • Security audit passed
  • Customer support ready
  • Pricing tiers finalized

Deliverable: General Availability

Milestone 5: Enterprise Ready

Target: January 2027

Criteria:

  • SSO working
  • SOC 2 Type II certified
  • On-premises option available
  • Advanced RBAC implemented
  • Enterprise SLAs defined
  • 24/7 support available

Deliverable: Enterprise Edition

📊 Development Metrics

Velocity Tracking

Current Sprint Velocity: ~20 story points/week

Team Size: 1-2 developers (current)

Planned Growth:

  • Q1 2025: 2-3 developers
  • Q2 2025: 3-4 developers
  • Q3 2025: 4-6 developers
  • Q4 2025: 6-8 developers

Code Quality Goals

Test Coverage:

  • Current: 60%
  • Target Q1: 70%
  • Target Q2: 80%
  • Target Q3: 85%
  • Target Q4: 90%

Code Review:

  • All PRs require review
  • Max 2 days to merge
  • No direct pushes to main

Technical Debt:

  • <10% of sprint capacity
  • Monthly tech debt review
  • Quarterly refactoring sprints

🚀 Release Schedule

Alpha Releases

Frequency: Weekly (internal)

Channels: Internal testing only

Versioning: 0.1.x

Communication: Internal Slack

Beta Releases

Frequency: Bi-weekly

Channels: Beta testers

Versioning: 0.2.x - 0.9.x

Communication: Email + in-app announcements

Features:

  • Feature flags for gradual rollout
  • A/B testing for new features
  • Beta feedback collection

Production Releases

Frequency: Monthly (after GA)

Channels: All users

Versioning: 1.x.x (semantic versioning)

Communication:

  • Release notes
  • Email announcements
  • Blog posts
  • Social media

Release Process:

  1. Feature freeze (1 week before)
  2. QA testing (3 days)
  3. Staging deployment (2 days)
  4. Production deployment (rolling)
  5. Monitoring period (24 hours)

🛣️ Long-term Vision

2026 Goals

  • Support 50,000+ users
  • 10,000+ paying customers
  • $1M+ ARR
  • Support 10+ programming languages
  • 20+ framework integrations
  • 99.99% uptime SLA
  • SOC 2 Type II certified
  • Series A funding raised

2027 Goals

  • Market leader in AI testing
  • 100,000+ users
  • $5M+ ARR
  • Mobile app testing
  • Performance testing suite
  • Visual testing platform
  • Full test automation platform
  • International expansion

📝 Notes

Assumptions

  • Team will grow as outlined
  • No major technical blockers
  • AI APIs remain stable
  • Market demand continues
  • Funding secured as needed

Risks

  • AI API rate limits or costs
  • Competition from larger players
  • Technical debt accumulation
  • Team turnover
  • Market adoption slower than expected

Mitigation Strategies

  • Multiple AI provider support
  • Focus on unique value propositions
  • Regular tech debt sprints
  • Strong team culture
  • Validated learning approach

🔗 Related Documentation

Reading this with an agent? /docs/roadmap/timeline.md serves the raw markdown.

All docs