Selected work

Project 1 of 4

Backend engineering · Business integrations · Zweidevs · 2025–2026

Tranero

Backend work across authentication, subscriptions, administration, integrations, and deployment.

Role
Backend developer at Zweidevs
Deliverable
Backend flows, integrations, and deployment
Focus
Authentication · subscriptions · business systems
Live site

Overview

At Zweidevs, I worked on the backend for Tranero, a platform for compliance, invoicing, and API integration. My contribution covered authentication, subscription flows, admin dashboard APIs, external accounting and ERP integrations, and deployment.

  • Authentication
  • Subscription flows
  • Admin APIs
  • QuickBooks
  • Microsoft Dynamics
  • Odoo
  • HOPtool
  • ERPNext
  • Invoice integrations
  • Helpdesk integrations
  • Deployments

Project flow

Architecture and flow.

5 connected stages

  1. 1access
  2. 2subscriptions
  3. 3admin
  4. 4integrations
  5. 5deployment

Product context

Tranero

Tranero · Public product site · Accessed 2026

The public site describes Tranero's compliance, invoicing, subscription, and ERP-integration scope. The contribution described here is limited to my backend work at Zweidevs.

testing.tranero.com

Visit the product site

Scope

Work completed and source material.

Scope and evidence

Scope and contribution.

This case study covers my backend contribution at Zweidevs. I did not design the public marketing site, and private source code, client data, credentials, and internal architecture are excluded.

  1. Worked on authentication and subscription flows.

  2. Built backend support for admin dashboard operations.

  3. Worked on QuickBooks, Odoo, HOPtool, and ERPNext invoice and helpdesk integrations, plus Microsoft Dynamics integrations.

  4. Handled deployment work for the application and integration changes.

Problem

Main technical constraint.

Problem framing

Connecting product and business-system workflows.

The backend needed to support authentication, subscriptions, and admin operations while connecting invoicing and helpdesk workflows across several external business systems.

Implementation

4 implementation steps.

Implementation

Backend implementation.

  1. Step1

    Worked on authentication and subscription flows.

  2. Step2

    Implemented backend services used by the admin dashboard.

  3. Step3

    Worked on QuickBooks, Odoo, HOPtool, ERPNext, and Microsoft Dynamics integrations.

  4. Step4

    Handled deployment work for the application and integration changes.

Result

Backend workflows and integrations.

My contribution covered account access, subscriptions, administrative operations, external integrations, and deployment work. Private implementation details and client data are excluded from this public summary.

What I learned

This project gave me practical experience across core backend flows, external business-system integrations, and deployment work.