Danobin.

Overview

The context behind the code.

Danobin was a startup where I served as CTO, combining technical direction with hands-on work on the core product. The work spanned product exploration, shared domain documentation, a core service, and a collaborative infographic interface.

The problem

The problem

A developing product needs its account, subscription, and credit behavior to stay coherent as features change: plan changes, recurring credit updates, and communication with users all have to agree.

Architecture

Architecture

The core service uses Django modules for users, subscriptions, and credits, with background tasks and a shared email service, alongside a separate Next.js interface.

Danobin's repositories are private; the diagram shows component responsibilities.

My contribution

My contribution

Alongside the CTO role, I implemented subscription-plan changes and credit management, documented the product's domain events, and built an email service with templates, asynchronous tasks, and tests.

Engineering challenges

Engineering challenges

Subscription changes affect credit allocation and scheduled work. Email delivery introduces a separate failure boundary. These concerns require coordination across the product's core behavior, beyond a single screen or endpoint.

Engineering reflections

Engineering reflections

The CTO role joined two kinds of work: deciding how the product's core should behave, and building those parts myself.

Technology

The tools behind the work.

• Python
• Django
• Background tasks
• Next.js
• React