NuxiPro Center | Blog

Migrated from GitHub to Codeberg

Fri, 02 Oct 2026 00:00:00 GMT

Why I migrated from GitHub to Codeberg?

I migrated from GitHub to Codeberg mainly because GitHub is a proprietary platform, which is a sovereignty issue for me (notably because their Copilot AI is trained on public code).

My main goal was to find simplicity: fewer unused features, a platform that gets straight to the point.

My steps to migrate my project from GitHub to Codeberg:

I used these commands to perform the migration:

# 1. Change the remote URL to point to Codeberg
git remote set-url origin https://codeberg.org/NuxiPro/Core.git

# 2. Push all branches and tags
git push --all
git push --tags

I could have used Codeberg’s native import tool, but since the NuxiPro Core repository was private, I preferred to do the transfer manually by choice. It took a few minutes and everything went very well.

What I gain and what I lose leaving GitHub for Codeberg

What I gain:

Everyday simplicity
No overload of unused features
Sovereignty (Codeberg is hosted in Germany by a European non-profit)
Ethics: no business model based on exploiting your code
A calmer, cleaner environment, without proprietary tools

What I lose:

Less visibility than on GitHub
Fewer out-of-the-box tools, but more control over what I add

Self-hosted Forgejo runner on my personal PC

I decided to self-host my own runner on my personal machine.

I use the Docker-in-Docker (DinD) strategy: jobs run in a separate Docker daemon, without direct access to my host’s Docker socket, which guarantees good isolation for my build environments.

I made this choice so I don’t saturate Codeberg’s shared community resources during my testing and deployment phases. Eventually, I will move this runner to a dedicated server so I no longer depend on my desktop PC.

Quick note about the demo

I kept the demo repository on GitHub for now, because it will very soon be stopped and deleted. Since it was a test version requiring unnecessary maintenance, it will be replaced directly. I will let you know before its final removal.

Building NuxiPro Cloud: What's new

Tue, 15 Sep 2026 00:00:00 GMT

I decided to make the Cloud version of NuxiPro secure and minimalist on a day-to-day basis, so I never have to worry about the tool itself, especially since it will store my own personal and professional data.

For now, this version of my project isn’t ready or functional enough yet to handle real, critical data in production.

My backend tech stack

Here are the technologies I’ve added to Cloud NuxiPro:

Better Auth (for authentication)
Drizzle (ORM for PostgreSQL)
Hono (for the backend server)
Fractional indexing (for managing task position on the Kanban board)
Nginx (reverse proxy planned in front of the backend before Cloud NuxiPro launches)
TypeScript (main backend language)
Bun (runtime to run the backend)
date-fns (for date handling)
Zod / Hono validator (for validating incoming and outgoing data)
OpenObserve (for centralized log management)

Why this choice for the backend?

I chose this stack to make NuxiPro efficient, predictable, and to guarantee resilient security. Since I’ll be storing my own data there, and I regularly see SaaS products get hacked, I refused to be next on that list. My goal is to build a system where users are safe thanks to a sovereign tool, hosted in Finland with UpCloud (sovereign, performant, and very appealing in terms of price).

I went with Hono and Better Auth because they’re simple to use, highly efficient, and help me build solid security.

I also integrated Fractional indexing to manage card position on the Kanban board as efficiently as possible. It lets you drag and drop a task between two columns or above another one without having to rewrite the value of every other task. In short, it avoids collisions while keeping things smooth day to day.

To centralize my logs and handle errors, I use OpenObserve. The goal is to spot and fix crashes very quickly. Even before the Cloud version ships, I’m going to run a battery of intensive tests with the explicit goal of trying to crash the system. That will let me confirm it’s truly robust. Of course, that won’t rule out 100% of future bugs, but these crash tests will prove the tool’s solidity.

My frontend tech stack

TypeScript (for simplicity and type safety)
TanStack Router / Query (for handling dynamic pages and state)
React (for building the user interface)
Zod & React Hook Form (for validating form input data)
shadcn/ui (so I don’t recreate the interface from scratch and waste time on pointless UI bugs)
Tiptap (for building the Markdown editor)
dnd kit (for smooth drag & drop in the Kanban board)
Bun, Vite & Hono Client (for building, bundling, and communicating with the API)

Why this choice for the frontend?

I chose this stack because it’s simple, maintainable over the long run, and built to last several years without becoming obsolete.

Why did I choose this overall stack?

I designed this stack mainly to build an efficient, simple daily work tool, free of unnecessary visual noise that wastes time.

My priority was (and still is) a tool suited to people who work solo. Nowadays, most software keeps piling on features instead of simplifying, which creates friction on a daily basis.

Being someone very demanding about security, performance, and freedom from bugs, I want my own work tool to be ultra-efficient and require zero energy to manage. NuxiPro is here to serve me every day, both in my professional and personal projects.

Sovereignty & Compliance

Fri, 28 Aug 2026 00:00:00 GMT

I am currently focusing on sovereignty and compliance for NuxiPro. My goal is to build a truly helpful, privacy-first tool that respects user data.

Here is the roadmap I am executing before pushing forward with NuxiPro’s cloud version:

GDPR Compliance: Clearly document data storage locations, processing methods, and third-party sub-processors.
Legal Hub: Centralize all legal and compliance documents directly on the landing page.
GDPR Traceability: Implement a strategy to track user consent, permissions, and privacy preferences accurately.

Ultimately, my goal is to deliver a sovereign, privacy-respecting, minimalist alternative to Trello.

Introducing NuxiPro

Wed, 19 Aug 2026 00:00:00 GMT

What is NuxiPro?

NuxiPro is a minimalist, lightweight task manager with no unnecessary features that clutter your workspace. Its core purpose is to create a self-cleaning workspace — tasks that reach “Done” are archived automatically.

Most Kanban tools make it easy to add tasks and features, but none keep your workspace clean and clutter-free. NuxiPro solves this problem.

The Problem

Today’s tools help us add tasks, but none help us remove them. Without automatic cleanup, the “Done” column becomes a graveyard of cards. We waste precious time figuring out how to archive and cleaning up manually, instead of moving our project forward.

I built NuxiPro to offer a simple, minimalist Kanban that’s ready to use. As soon as a task slides into the “Done” column, it’s instantly archived in the background. Minimal configuration, zero complexity, and your board stays clean from day one.

How it works

Instant archiving (demo): Tasks archive instantly when moved to Done. Data stays in your browser (localStorage).
Configurable archiving (cloud): Choose your archiving mode — instant or time-based (X days). Persistent server storage.

Key Features

Zero friction — Manual archiving disappears completely
Zero visual clutter — No more completed tasks polluting your workspace
Simple tracking — Visualize your progress and daily wins, effortlessly
No useless features — Focus on what matters without being overwhelmed
Quick start — A tool ready to use, simple day-to-day

Demo vs Cloud

	Demo	Cloud
Archiving mode	Instant only	Instant or time-based
Data storage	Browser localStorage	Server-side (persistent)
Intended use	Discovery	Production, real daily use
Account required	No	Yes

Try it

Try the live demo without creating an account.

NuxiPro Cloud — Coming Soon

The Cloud version of NuxiPro (app.nuxipro.com) is currently in development.

What NuxiPro Cloud will offer

Secure data storage — Your data is stored in a database, not in the browser’s localStorage
Data sovereignty — You own your data, always
Multi-project support — Each project appears as a line in the sidebar with its own name
Auto-archiving of completed tasks — Finished tasks are automatically moved to the archive
Minimalist tools — No useless features you’ll never use
Dedicated account — One account per user
Workspaces — Switch between workspaces without losing time
Low configuration — Choose your archiving mode at setup, change it anytime

How archiving works in Cloud

Two modes to choose from:

Instant — Task archives immediately when moved to “Done”
Time-based — Task archives after X days (configurable)

Your tasks are visually separated from your workspace. Completed tasks move to a dedicated archive zone without being loaded when you open your project — avoiding performance issues.

Your workspace stays clean, free of visual clutter from completed tasks. You can always find your archived tasks in the archive zone without ever losing them.

Why the demo is not made for real projects

The demo is designed for demonstration only. If you store sensitive data, you may lose it permanently because storage is done in your browser (localStorage). The Cloud version solves this with persistent server-side storage.

Demo vs Cloud

	Demo	Cloud
Data storage	Browser localStorage (may be lost)	Database (persistent)
Archiving mode	Instant only	Instant or time-based
Projects	Single project	Multi-project
Workspaces	No	Yes
Account	No	Yes
Configuration	None	Choose archiving mode at setup
Intended use	Discovery	Production, real daily use

Join the waitlist

The Cloud version will launch with a pre-release for early testers. Join the waitlist at demo.nuxipro.com — Sébastien Babas will personally notify you when the pre-release is about to launch.

Your feedback will directly shape how NuxiPro Cloud gets built.

Follow the development

Blog — Follow this (blog)[https://center.nuxipro.com] for updates on NuxiPro Cloud
Dev.to — Follow @sbabas for technical content
Twitter — @Tybass450
Email — contact@nuxipro.com

Built by Sébastien Babas — Designed for absolute mental clarity.

NuxiPro Center | Blog

Migrated from GitHub to Codeberg

Why I migrated from GitHub to Codeberg?

My steps to migrate my project from GitHub to Codeberg:

What I gain and what I lose leaving GitHub for Codeberg

What I gain:

What I lose:

Self-hosted Forgejo runner on my personal PC

Quick note about the demo

Sign up to follow NuxiPro Cloud progress

Building NuxiPro Cloud: What's new

My backend tech stack

Why this choice for the backend?

My frontend tech stack

Why this choice for the frontend?

Why did I choose this overall stack?

Sign up to follow NuxiPro Cloud progress

Sovereignty & Compliance

Sign up to follow NuxiPro Cloud progress

Introducing NuxiPro

What is NuxiPro?

The Problem

How it works

Key Features

Demo vs Cloud

Try it

NuxiPro Cloud — Coming Soon

What NuxiPro Cloud will offer

How archiving works in Cloud

Why the demo is not made for real projects

Demo vs Cloud

Join the waitlist

Follow the development

Sign up to follow NuxiPro Cloud progress