SYSTEMS ANALYST
& DEVELOPER.

I am Froaky. I design high-performance APIs and internal operations tools that bridge business logic with reliable technology.

AVAILABLE // REMOTE

Full-Stack Dev

Salta, Argentina

INIT_WORK_VIEW

GET_RESUME [VERSION_WEB]

4h → 5min

Daily manual sync (Odoo Hub)

100%

Spreadsheets replaced (Gerayse)

Systems in production

ANALYSIS_CORE

Operational Analysis

Data Auditing & Integrity

Process Cycle Optimization

Multi-tenant Architecture

Legacy System Migration

CAPABILITIES.MANIFEST

Solving Complex Operational Challenges.

MOD::API_INTEGRATION

APIs & Integrations

Architecting robust RESTful and GraphQL services. Specialized in connecting legacy systems like Odoo with modern cloud infrastructure.

MOD::INTERNAL_OPS

Internal Tools

Developing specialized internal applications that streamline workflows, reduce manual data entry, and increase team efficiency.

MOD::SYS_STRUCT

System Design

Designing scalable SQL-backed systems with clean data modeling, optimized indexing, and maintainable architectures.

PROCESS.PIPELINE

How I Work.

[01]

ANALYZE

Map the real process first — data flows, roles and bottlenecks — before writing a single line of code.

[02]

MODEL

Turn business rules into explicit models: state machines, SQL schemas, permission levels.

[03]

BUILD

APIs and internal tools on a pragmatic stack, built to be maintained by whoever comes next.

[04]

OPERATE

Deploy, monitor and iterate with the team until the process runs on its own.

BIOMETRIC.BIO

About the Analyst.

I specialize in transforming operational chaos into structured, high-performance software. My background as a Systems Analyst allows me to look beyond the code and understand the business flow, ensuring that every integration serves a strategic purpose. I don't just build apps; I build engines that power business growth.

ROLESystems Analyst & Developer

BASESalta, Argentina (Remote)

FOCUSBackend, APIs & Internal Ops

SYSTEM.SPECS

Technical Stack.

Relational DB

SQL

ACTIVE

SQLModel

BACKEND CORE

ORM / Types

ACTIVE

Prisma

BACKEND CORE

FRONTEND MOBILE

Animations

// OPERATIONAL_TOOLS

ACTIVE

Git/GitHub

OPERATIONAL TOOLS

Version Control

ACTIVE

Docker

OPERATIONAL TOOLS

Containers

ACTIVE

Railway/Vercel

OPERATIONAL TOOLS

PaaS Deploy

XLS

ACTIVE

Excel Automation

OPERATIONAL TOOLS

Python scripts

ACTIVE

API Auditing

OPERATIONAL TOOLS

Sec & Perf

ARCHIVE.PROJECTS

Featured Work.

OBRASTAFF

Documentary-compliance platform for mining, construction and industrial assembly. A single centralized eligibility rule decides — with a traffic light — who is cleared to enter a site.

Encoding safety-critical compliance as one rule reused by web, API, dashboard and reports.

The clearance decision is written once and surfaced right at the site gate — no screen recomputes it.

Laravel 12Livewire 3PostgreSQLSanctum API

VISIT_SITETECHNICAL_SPECS

obrastaff-production.up.railway.app

ENGINEERING_DECISIONSOBRASTAFF

PROBLEM ▸The clearance rule is safety-critical — if each screen recomputes it, they drift and someone enters with an expired certificate.

DECISION ▸A single Action, CheckEmployeeEligibilityForProject, owns the rule and returns a typed DTO; web, API, dashboard and reports all consume it.

PROBLEM ▸'Approved' documents expire silently — a valid-looking certificate can be past its date.

DECISION ▸One DocumentStatusService derives the effective status (approved + past date = expired), so a date is never compared by hand in two places.

PROBLEM ▸Personnel documents are sensitive and roles range from HR to external auditors.

DECISION ▸Files live on a private disk served only through Policies; authorization asks for one of ~22 granular permissions, never a hardcoded role.

SALTA RUBIK

Product-oriented Flutter system for speedcubers. Features WCA scrambles, session history, and a Fastify/PostgreSQL backend.

Precise timing & state sync across web/mobile platforms.

Deployed a production-ready tool with WCA-style compliance.

FlutterFastifyPrismaPostgreSQL

VISIT_SITETECHNICAL_SPECS

timer-salta-rubik-production.up.railway.app

ENGINEERING_DECISIONSSALTA_RUBIK

PROBLEM ▸Timing must be millisecond-precise on both web and mobile, without drifting between devices.

DECISION ▸Custom synchronization engine on Fastify + Prisma that reconciles solve history across devices.

PROBLEM ▸Scrambles must be valid for competition-style practice.

DECISION ▸WCA-style scramble engine instead of naive random move generation.

PROBLEM ▸Stats over thousands of solves get slow if computed naively.

DECISION ▸Session-based history model in PostgreSQL with precomputed trend statistics.

GERAYSE

Financial operations engine replacing legacy spreadsheets. Manages branch cashflow, treasury, and cross-office auditing.

Translating manual Excel chaos into auditable business rules.

Eliminated 100% of spreadsheet dependency for core operations.

DjangoPostgreSQLHTMXOperational UI

VISIT_SITETECHNICAL_SPECS

gerayse10-production.up.railway.app

ENGINEERING_DECISIONSGERAYSE

PROBLEM ▸Core financial operations lived in editable spreadsheets with no audit trail.

DECISION ▸Business rules modeled in Django over PostgreSQL, so every movement is validated and traceable.

PROBLEM ▸Multiple offices handling cash with different levels of responsibility.

DECISION ▸Centralized branch treasury with a multi-level permission system.

PROBLEM ▸Manual end-of-day closings were slow and error-prone.

DECISION ▸Automated daily financial closing that locks the day's ledger.

KINNIKU APP

Multi-tenant SaaS for gym management. Includes QR check-ins, automated subscription flows, and white-label branding.

Strict data isolation & dynamic branding for multi-tenant scaling.

Scalable SaaS infrastructure ready for commercial multi-gym rollout.

FastAPISQLModelSaaS ArchitectureQR-Core

VISIT_SITETECHNICAL_SPECS

kinnikuapp.com

ENGINEERING_DECISIONSKINNIKUAPP

PROBLEM ▸Many gyms on one platform — one tenant's data must never leak into another's.

DECISION ▸Strict multi-tenant isolation enforced at the data layer in FastAPI + PostgreSQL.

PROBLEM ▸Front-desk attendance control has to be faster than a paper list.

DECISION ▸QR check-in flow validated server-side against the member's subscription.

PROBLEM ▸Each gym wants the app to look like their own brand.

DECISION ▸White-label theming resolved per tenant at runtime.

OPSFLOW (Internal)

Internal operations dashboard for managing complex business logic and real-time process tracking.

Modeling complex supply chain approval chains as state machines.

Streamlined internal approval latency by reducing manual overhead.

Next.jsServer ActionsIndustrial UX

VIEW_DEMOTECHNICAL_SPECS

internal://opsflow — live demo

OPSFLOW (Internal) — real product screenshot

ENGINEERING_DECISIONSOPSFLOW

PROBLEM ▸Approval chains encoded in ad-hoc conditionals become impossible to reason about.

DECISION ▸Each request lifecycle modeled as an explicit state machine — invalid transitions can't happen.

PROBLEM ▸Bottlenecks were invisible until someone complained.

DECISION ▸Real-time monitoring of every request's state, surfaced in a technical dashboard.

PROBLEM ▸Every state change needs accountability.

DECISION ▸Each transition is authorized and recorded before it's applied.

ODOO INTEGRATION HUB

Custom Odoo ERP modules exposing a restricted REST API that syncs field devices with the central ERP in real time.

Real-time device-to-ERP sync without breaking single-source-of-truth integrity.

Manual synchronization reduced from 4 hours daily to under 5 minutes.

PythonOdooPostgreSQLREST APIs

TECHNICAL_SPECS

ENGINEERING_DECISIONSODOO_INTEGRATION_HUB

PROBLEM ▸Field data was re-typed by hand into the ERP, delaying inventory and financial reporting.

DECISION ▸A restricted REST API over custom Odoo modules lets field devices sync in real time.

PROBLEM ▸A standalone middleware would duplicate business data outside the ERP.

DECISION ▸Built inside Odoo to keep a single source of truth, accepting the ORM's complexity under high load.

PROBLEM ▸High-frequency writes from field devices strained the database.

DECISION ▸PostgreSQL indexing optimized specifically for the hot write paths.