Open Sourcing FortyOne: Agentic Project Management With an AI Teammate

Source: Dev.to

What I mean by “agentic project management”

There’s a lot of “AI for project management” content out there, and most of it is basically:

You ask a question → you get a summary.

That’s useful, but it’s not agentic.

When I say agentic, I mean the AI is built to help with action inside your workflow, not just commentary about the workflow.

A few examples of the kind of work Maya is meant to support

That’s the “AI teammate” framing I’m pushing for: less chatbot, more “help me execute.”

What is FortyOne today?

FortyOne is a modern project‑management platform that focuses on:

• Stories – task tracking with real workflows
• Sprints – planning and velocity
• Objectives & OKRs – goal tracking tied to execution
• Real‑time collaboration – your team stays in sync

It’s designed to feel clean, fast, and easy to adopt.

What’s open source?

FortyOne is split into two main codebases:

• Frontend – fortyone.app
• Backend – api.fortyone.app

I’m sharing both because I want this to be genuinely useful for builders who want to learn from it, extend it, self‑host it, or contribute features back.

Frontend overview (fortyone.app)

The frontend is a Turborepo monorepo built for a real product, not a demo. It includes:

• A marketing & auth app
• The core project‑management app
• A docs site
• A React Native mobile app (in progress)

Stack (modern & practical)

• Next.js 15 + React 19
• TypeScript
• Tailwind CSS
• Radix UI + Framer Motion
• PostHog (analytics)
• NextAuth (authentication)

Monorepo structure (high level)

apps/
  landing/   – marketing + auth
  docs/      – documentation
  projects/  – core app
  mobile/    – React Native

packages/
  ui/        – shared UI components
  utils/     – shared utilities
  icons/
  configs/   – shared configs

Backend overview (api.fortyone.app)

The backend is a Go application that powers the core product workflows. It follows a clear architecture to make maintenance, testing, and extension easier.

Architecture (hexagonal / layered)

Highlights

• Migrations with golang-migrate
• Database seeding for quick dev setup
• Worker process for background work
• Brevo integration for onboarding & transactional emails

Local development

I wanted the project to be something you can actually run locally without a week of archaeology.

Frontend: run locally

# Clone the repo
git clone https://github.com/complexus-tech/fortyone.app
cd fortyone.app

# Install dependencies
pnpm install

# Copy environment files
cp apps/landing/.env.example apps/landing/.env
cp apps/projects/.env.example apps/projects/.env
cp apps/mobile/.env.example apps/mobile/.env

# Start dev server
pnpm dev

Backend: run locally

# Clone the repo
git clone https://github.com/complexus-tech/api.fortyone.app
cd api.fortyone.app

# Copy env file
cp .env.example .env

# Run the API (hot reload)
make dev

# In another terminal, run the worker
make worker

Migrations

Install the migrate CLI (if you want to work with migrations):

go install -tags 'postgres' github.com/golang-migrate/migrate/v4/cmd/migrate@v4.18.3

Run migrations:

make migrate-up          # apply all pending migrations
make migrate-down n=1    # roll back the last migration

Seeding

A quick way to get a working workspace:

# Default seed
make seed

# Custom seed
make seed name="My Project" slug="my-project" email="me@example.com" fullname="Your Name"

Why I open‑sourced it

1. Learn from a real product – not a toy “todo app,” but something with real trade‑offs, constraints, and structure.
2. Encourage contributions – not just PRs, but feedback on architecture, UX decisions, and what people want from agentic workflows.
3. Build in public – it’s easier to grow something when people can see it, use it, and improve it with you.
4. Agentic UX is the next frontier – after a decade of dashboards, the next step is software that can actually help you execute.

About the license

Both repositories include a LICENSE file in the root. The intent is:

• Free for personal and non‑commercial use.
• Commercial licensing required for larger businesses (as defined in the license).

If you’re building something commercial on top of it, read the license first and reach out if needed.

What I’d love help with

If you want to contribute, here are the kinds of contributions that are genuinely helpful:

• Fixing bugs and rough edges (especially around local setup)
• UI/UX polish and accessibility improvements
• Better docs and examples
• New features that enhance the agentic workflow
• Architectural feedback or design discussions

Thank you for checking out FortyOne! Feel free to open issues, submit PRs, or just give feedback. Let’s build the next generation of project‑management tools together.

Maya‑style workflows

• Integrations (GitHub, Slack, webhooks)
• Performance improvements and profiling notes
• Mobile app progress (React Native)

Even if you don’t want to write code, opening issues with clear reproduction steps and screenshots helps a lot.

Try it, star it, break it

If you’re curious about agentic workflows in a real project tool:

• Try the hosted version
• Star the repos if you want to follow progress
• Open an issue if something feels off
• Share ideas for what an “AI teammate” should do inside a PM tool—I want to hear them!

This is the direction I’m betting on: project management that helps you ship, not just report.

See you in the issues.