NEXA: lightweight, integrated tools for projects and support.

Every day we manage projects and run support. The tools for that — the market ones — are powerful but heavy: expensive, full of options nobody uses, slow to adopt. In the end you bend your process to the tool, not the other way round.

The idea was simple: build the tools we'd actually want to use — focused on what matters, light to adopt — and offer them to those who feel the same pain. We called them NEXA.

“Building our own tools” almost always dies: it becomes a side project that never reaches the polish and reliability of real software, or it turns into a maintenance burden. To be a real alternative — and to hand it to clients — it had to be production-grade: authentication, roles and permissions, notifications, SLAs, integrations. Not an internal toy.

We built a shared foundation — same stack (Next.js, Postgres), same design, same authentication, same bilingual setup, same notifications — and products on top of it.

The first: a Jira-style project and work manager, without the weight. Projects, work items with configurable types and states, hierarchy and dependencies, table, board and timeline views, sprints (with rollover of unfinished work), releases and per-project documentation.

The second: a helpdesk. Tickets with KPIs and filters, automatically monitored SLAs, real permissions on the API. Support without the complexity of the big players.

Two principles run through everything. First, we used them on our own operation — and only what survives daily use stays. Second, integration from the start: webhooks, inbound email that becomes a comment, email notifications — so they fit into what already exists, instead of being one more island. There's a dedicated client role, to open access to those who work with us.

Today there are two NEXA products in use — internally and with clients — on a shared base ready to take more. The helpdesk is still young; the project manager already runs our day to day.

If you pay a lot for software you use 20% of, and bend your process to fit it, there's room for the opposite: tools that fit you and connect to what you already have. That's what we're building.