Show HN: Ajen – Open-source platform where AI employees build your startup(github.com)
1 pointby yash_chudasama2 days ago4 comments
  • yash_chudasama2 days ago
    Since this is open source, I'm still debating what Ajen should ultimately become.

    One direction is turning it into a framework for building multi-agent companies, where developers can define roles, coordination logic, shared memory, and decision systems between AI employees.

    The other direction is making it a product for founders, where you describe a startup and AI employees (CEO, CTO, CMO, etc.) collaborate to plan and build the company — writing product specs, designing the architecture, shipping the product, and planning the GTM strategy.

    I'm curious which direction would be more interesting:

    • Infrastructure for building AI organizations • A practical AI co-founder product for founders

    Also wondering whether the system should eventually include roles like finance, legal, operations, etc., or if it's better to keep the core roles minimal and let people define custom AI employees.

  • yash_chudasama2 days ago
    Since it's day 1, a lot of things are still rough.

    I'm intentionally building this in the open so people can see the architecture evolve and suggest better approaches.

  • yash_chudasama2 days ago
    If anyone wants to contribute or experiment with ajne.dev, I'd love PRs.

    One idea I'm exploring is letting people define custom "AI employees".

  • vahid7862 days ago

      Cool concept. The multi-agent approach with role-specific AI employees (CEO, CTO, CMO) is interesting — reminds me of CrewAI but more startup-focused.                                                       
                                                                                                                                                                                                               
  A few thoughts:                                                                                                                                                                                            
                                         
  - How do the agents handle disagreements? For example, if the CTO agent wants to build a monolith but the CEO agent pushes for microservices based on scaling assumptions. Is there a conflict resolution
  mechanism?
  - The "custom AI employees" idea has legs. Different startups need different roles — a SaaS company needs a DevOps agent, an e-commerce one needs a supply chain agent.
  - For day 1 this is solid. Architecture suggestion: consider adding a shared context/memory layer so agents can reference what other agents decided. Without that, each agent works in a silo.

  Good luck with the project.
    • yash_chudasama2 days ago
      Thanks! Really appreciate the thoughtful feedback.

      I’m thinking of handling this through separation of concerns + domain expertise. Each AI employee would have a defined domain of authority. When disagreements happen, the system can score proposals based on expertise weighting, meaning the opinion of the domain expert carries more weight in that area.

      For example, if it's an architecture decision, the CTO's score would dominate, while the CEO focuses more on strategy and constraints rather than the implementation details.

      It’s still very early (literally day 1 ), so feedback like this is really helpful in shaping the architecture.

      Thanks again for taking the time to write this.