arthur regiani.EN/PT

Solutions Architect · OptikAI

Real systems.From ideato operation.

I connect software, data and cloud. From the incoming message to the application someone uses every day.

Explore my workLet’s talk
An abstract dark ceramic landscape: six topographic strata, a winding valley and fine copper paths.
ATLAS / 001

Cartography of a system01 / Connect

↓   Scroll to exploreSOFTWARE / DATA / CLOUD

01 — Selected work

Architecture meets practice.

Decisions, code and operations are part of the same work. These are some of the contexts where I bring those parts together.

Professional experience · current role

OptikAI/01

From incoming signals to useful information.

Architecture and development of a platform connecting web applications, equipment messages, asynchronous processing, AI inference results and dashboards.

  • Solution architecture
  • Integrations
  • Data
  • Operations
Explore the context
My contribution

I work on message ingestion and processing, services and interfaces. My scope also includes authentication and permissions, PostgreSQL modelling and queries, integrations, internationalisation, deployment and observability.

Decisions and direction

Consider the full data journey: separate ingestion from processing, organise contracts between services and make information accessible to people operating the application.

Current role. Public description of responsibilities, without client data or proprietary details.

Independent project · in development

CoffeeHub/02

Building to understand the field.

An app and API project exploring management and traceability in coffee farming, connecting agricultural workflows to software.

  • React Native
  • Django / DRF
  • PostgreSQL
Explore the context
My contribution

The repository contains a React Native application and a Django/DRF backend, with models and endpoints for agricultural operations.

Decisions and direction

Separate the mobile experience from the API and organise the domain in modules. Full traceability guides the project, but does not describe a completed product.

In development: some screens use mock data and several flows remain incomplete. Public code; production operation has not been verified.

Explore the code ↗

02 — How I think and build

The parts matter.So do the connections.

A system makes sense when information follows a clear path. This is the journey I focus on.

  1. 01

    Receive

    Understand the message, validate its structure and define integration contracts.

  2. 02

    Process

    Organise rules, asynchronous tasks and persisted data with context.

  3. 03

    Deliver

    Connect services and interfaces to turn data into usable information.

  4. 04

    Operate

    Follow logs, permissions, deployments and behaviour after delivery.

My scope starts with received messages. Hardware, core firmware and authorship of all AI models are outside that attribution.

An abstract dark ceramic landscape: six topographic strata, a winding valley and fine copper paths.

Cartography of a system02 / Explore

03 — Personal lab

Room for curiosity. Space to experiment.

Not every exploration needs to become a product. Some start as a question, become an experiment and change how I solve the next problem.

01

Experimental environment

Linux & self-hosting

NixOS, Linux, containers and automation to investigate how services behave outside ideal conditions.

02

Private experiment · MCP

Personal OS — Local

MCP tools for local diagnostics and automation. A space to explore boundaries, permissions and the relationship between agents and the operating system.

03

Hands-on research

Local AI

Local models, agents and development tools. I explore combinations, compare possibilities and apply what I learn to concrete problems.

04 — About

I learn by building. I build by connecting.

I’m Arthur José Regiani, a Solutions Architect at OptikAI. My work combines software development and infrastructure: I like understanding what happens between interfaces, data and operations.

I work with TypeScript and JavaScript, React and Next.js, Node.js, PostgreSQL and cloud services. Understanding the problem comes before choosing the tools.

I enjoy combining technologies, testing hypotheses and observing working systems. My personal lab builds that repertoire; practice gives those choices context.

Current focus

  • System architecture and integration
  • Applications, data and asynchronous processing
  • Deployment, observability and operations

05 — Next connection

The next systemstarts witha conversation.

Working on a project or a technical problem? Let’s understand the context and think through the next steps.

GitHub ↗LinkedIn ↗

An abstract dark ceramic landscape: six topographic strata, a winding valley and fine copper paths.

Cartography of a system03 / Compose