Azaeron

What the product does

Azaeron is a merchant workspace for invoices, quotations, payments, inventory and customer records. Those tasks share financial state, so one screen cannot decide alone when an invoice is paid.

The problem it addresses

Billing software must stop invalid transitions and preserve a clear record when business state changes. A paid invoice cannot be inferred from a button click or a browser return value.

What was built

I worked across the React interface, Express API, business rules and release checks. The invoice lifecycle service checks allowed transitions and payment summaries before recording a change.

Decisions that shape the work

How the pieces connect

The browser presents merchant workflows. The API validates identity, tenant scope and permissions before changing records in MongoDB. Invoice transitions also write audit and financial journal events.

1. 01Browser

   React + TypeScript/Vite interface for invoicing, POS, and merchant operations.

2. 02API

   Express routes, validation, role permissions, lifecycle rules, and rate limits.

3. 03Data

   MongoDB/Mongoose models; invoices carry payment and lifecycle state.

4. 04Delivery

   GitHub Actions release checks; separate Vercel frontend and Render API configuration.

How it was checked

The code includes lifecycle rules, authorization middleware, database index checks at startup and a GitHub Actions release gate. The sign-in and documentation pages are available online.

Where the work stands

What remains unconfirmed

• Authenticated production flows and active integrations have not been independently inspected.