LUdev logo
Back to portfolio

Air2Tree

1 / 2

The project

The Project AirToTree (A2T) addresses the complex challenge of atmospheric CO2 removal by acting as an intermediary, dual-sided marketplace. It connects European landowners with institutions striving to fulfill ambitious net-zero goals.

Our project focused on building a robust platform that streamlines user acquisition while supporting the Measuring, Reporting, and Verification (MRV) infrastructure necessary for carbon quantification. The system features:

  • Role-based interactive dashboards for sellers, buyers, supporters, and administrators.
  • Automated onboarding flows.
  • A Carbon Removal Unit (CRU) computation pipeline.

The customer

The Customer Our client, Attila Turos, is the CEO and Founder of the AirToTree startup. His company operates as an early adopter of the EU Carbon Removal Certification Framework (CRCF).

The Challenge: Ensuring that every carbon removal project meets strict EU-wide quality criteria for long-term storage and Corporate Sustainability Reporting Directive (CSRD) disclosure.

Our Collaboration: The project was developed in close collaboration with the client and his team. The project shifted in scope multiple times but we were able to effectively naviagate it through constant comunication, through weekly meetings and refinement sessions, even working alongside A2T’s senior developer to review initial database schemas and ensure our development perfectly aligned with their expectations.

The team

The Team Our team operated within an Agile workflow across eight sprints.

Key Roles

  • Scrum Master (Rares): Facilitated meetings and removed impediments to keep the team moving.
  • Product Owner (Dylan): Prioritized the GitHub Project Board backlog and distributed the workload.

Development Focus We divided the work based on our core strengths:

  • UI/UX & Frontend: Bilal and Arya
  • Backend & MRV Architecture: Dian, Artemij, and Rares
  • Full-stack & CI/CD: Dylan

Challenges & Triumphs We faced two major challenges during development:

  1. An initial lack of repository permissions that delayed our first sprint.
  2. A massive mid-project scope change from the client that required us to pivot toward a heavy MRV-oriented architecture.

As a team, we are most proud of successfully navigating an inherited, unfamiliar codebase and establishing a highly stable, technical foundation that helps forest conservation.

The technologies

  • The Technologies
  • Frontend
  • Figma (UI/UX mockups)
  • React and TypeScript (Formatted consistently via Prettier)
  • Backend & Database
  • Python 3.13
  • PostgreSQL (Production database management)
  • SQLite (Fully isolated, in-memory database testing)
  • Testing & CI/CD
  • Pytest, pytest-asyncio, and pytest-cov (Backend unit testing)
  • GitHub Actions (Three workflows for automated deployment and code quality enforcement)
  • AWS S3 & Elastic Beanstalk (Production deployments and shareable application bundles managed via AWS CLI)
  • Tools
  • Git / GitHub (Version control and project board tracking)
  • npm (Package management)
  • Ruff (Python linting and formatting)