Available for on-demand projects

The story of turning support, servers, and AI into real engineering.

I am Emanuel Missena, known in the tech and open-source communities under the codename Emanuel Vini (emanuelVINI01). I am a 16-year-old full-stack developer. Before using AI to accelerate delivery, I was already waking up to fix servers, debugging Java plugins, automating Discord support, and writing code that had to work for real clients. My stack ranges from low-level systems with Rust VMs and bare-metal servers to high-level product engineering, building modern systems, RESTful APIs, Docker, and cutting-edge automation. That exact friction between infrastructure and product shaped the engineer I am today.

View projects Public GitHub

Direct contactcontact@emanuelvini.dev

Original public repos

Verified via the public GitHub API

2021

First public proof

Java plugins created on GitHub in June 2021

Current focus

Next.js, Prisma, applied AI, and transactional systems

portfolio://quality-scan

real commands, auditable signals, and motion-first UX

Operational Stack

emanuel@portfolio~/prod$npm run lint

02=> interface validated: motion, responsive layout, filters, and project modal

emanuel@portfolio~/prod$npm run build

04=> Next.js 16 + React 19 + Tailwind CSS shipping an auditable portfolio

emanuel@portfolio~/prod$open /projects --spotlight my-bet

06=> priority: stateful/stateless separation, transactional ledger, and Redis locks

portfolio ready for review

awaiting

VERIFIED ENGINEER PROFILE

Emanuel ViniEmanuelMissena

Full-Stack Engineer · Age 16

LOW-LEVELHIGH-LEVEL

building since 2020 · Santos, BR

About Me

Emanuel Missena (Emanuel Vini)

Learn about my origins, my background, and what drives me to build real software engineering.

Hey — I'm Emanuel Missena, from Santos, SP, Brazil. Italian roots, Santos upbringing. Online I go by Emanuel Vini or @emanuelVINI01, the alias I've used since I started coding. I was running servers at 10, no courses, just trial and error and a lot of broken configs.

Started doing Minecraft server support, moved to Discord bots and Java plugins, then pushed further into REST APIs, transactional systems and applied AI. No degree — just built things until they worked, then built harder things. That gap shows up in the code.

Skills

My Stack and Tools

What I actually use — no filler.

Next.js

Prisma

AWS

AI Management & Claude

GitHub

Advanced Linux

Docker

Redis

Zod

Java

Kotlin

Technical Story

It started as curiosity. It became operations. Today it became product.

The story below is designed to read like an investigation: every chapter shows real pressure, the technical decision behind it, and the public trail that helps audit the journey.

The opening

I did not enter tech through polished tutorials. I entered because something broke and someone had to fix it.

In 2020, isolation became a lab. I started with Java, Minecraft, .jar files, plugin.yml, and stack traces that did not explain anything gently. The only path was to read, test, break things, and compile again.

The beginning was not clean. There was coupled code, bad naming, API guesswork, and many attempts that failed in the console. But every error forced an investigation: old forums, incomplete wikis, official documentation, forgotten issues, and technical conversations in languages I was still learning.

Then the code left the hobby phase and entered operations. Dedicated server, VM, panel, customer, payment, ticket, route, uptime. When customers are waiting, architecture stops being a nice word and becomes survival.

That phase trained the skill that separates average developers from strong ones: looking at a broken system without freezing, reducing the problem, testing hypotheses, and turning mess into architecture.

Today I use AI, vibecoding, and agents as accelerators. But the foundation behind the decisions came from somewhere else: console output, Linux, APIs, databases, networks, and responsibility for systems that could not simply go down.

Roots

The curve started with errors

The foundation came from documentation, forums, wikis, compilation errors, and reading existing code. The early code was not perfect; refactoring what I broke myself built technical judgment.

Infra

Operations raised the stakes

Servers, virtual machines, panels, routes, resource limits, and uptime shaped a practical view of production systems.

Business

Payments punish bugs

Webhooks, payment gateways, and idempotency taught early that good backend work protects money, state, and trust.

Now

AI enters as scale

Vibecoding and multi-agent workflows act as scaling tools, not replacements for architecture, debugging, and technical judgment.

Chapter 03

ChatOps before I knew the name

The command center that moved half a terabyte of RAM into Discord.

Between ages 11 and 13, infrastructure stopped being a side project: two OVHCloud bare-metal dedicated servers, 256GB of RAM each, and customers opening tickets whenever a CPU spike looked like the end of the world. The bottleneck was no longer hardware. It was time.

Discord

TypeScript

OVHcloud

Linux

Cloudflare

GitHub

discord://infra-command-center

ChatOps before I knew the name

ChatOps

emanuel@portfolio~/prod$/node ovh-01 diagnose vm client-42

02=> cpu: spike detected | route: degraded | invoice: ok

emanuel@portfolio~/prod$/vm client-42 restart --graceful

04=> status: recovered | ticket: closed with incident note

incident stabilized

awaiting

512GB

RAM orchestrated

Two 256GB OVHCloud servers described in the operation.

24/7

real pressure

Tickets, maintenance, outages, routes, and support while school life continued.

API

not just chat

Bots acted as an operational interface for panels, instances, and customers.

The scene that explains everything

A customer opened a late-night ticket demanding SLA. On the other side, a 12-year-old picked up his phone, ran a private Discord command, checked the node, restarted a VM or killed a stuck process, answered like professional support, and went to school.

Ticket lands in Discord

Bot connects customer, invoice, and instance

Command calls API or Linux routine

Node responds, VM stabilizes, customer gets status

APIs as an invisible panel

The bot consumed Virtualizor and Pterodactyl REST routes with tokens, turning chat into an infrastructure cockpit.

Terminal inside the workflow

VM restarts, diagnostics, and stuck processes moved from manual SSH into restricted Discord commands.

Crisis alerts

Global warnings informed customers about maintenance, routing instability, uptime changes, and node incidents.

Finance connected to ops

Overdue invoices triggered alerts and could cut instance resources when the operational limit was crossed.

Public proof

Public trail connected to this chapter

The OVH/Virtualizor/Pterodactyl operation is an operational account. The auditable public trail lives in the Discord/Minecraft bots and integrations published on GitHub, and in the Rust VM that carries that same bare-metal obsession forward.

Large companies call this ChatOps: Slack or Teams connected to cloud operations for faster response. I built my version with Discord, TypeScript, APIs, and real servers because I needed to save time, reduce manual support, and keep customers online.

zDiscordCore

Java, created on Apr 30, 2022

ComuniMineBot

TypeScript, published on Aug 16, 2023

RyzenShopBot

TypeScript, published on Aug 16, 2023

MinecraftFeastBot

JavaScript, published on Aug 16, 2023

my-vm

Rust, bare-metal VM — the direct evolution of that hardware obsession

Services

Full-stack delivery with clear signals for technical teams.

The portfolio organizes real projects by architecture, product decisions, stack, and evaluation points: authentication, data modeling, APIs, dashboards, validation, deployment, and interface polish.

APIs and transactional systems

Rigorous contract modeling, data validation, end-to-end authentication, and consistency guarantees. Development of robust backends designed for extreme scalability and reliability.

Dashboards and web products

Construction of highly optimized and responsive dark interfaces. Transformation of complex requirements and technical workflows into clear metrics and high-value products.

Architecture and quality

Modular planning, strict separation of concerns, end-to-end strong typing, and establishment of deployment pipelines to ensure maintainability and continuous evolution of the codebase.

Engineering Spotlight

My Bet: iGaming Architecture

High concurrency and financial integrity at scale.

my-bet is a complete iGaming system running 13 original games, rigorously divided into three engines: Stateless (Dice, Plinko), Stateful (Mines, Dungeon) with Redis caching, and Real-time (Crash, Race) using SSE for simultaneous broadcasting.

It employs Redis for distributed locks to prevent double spending and features 8 native PIX gateway integrations. Balance operates strictly in integer cents through an auditable ledger with idempotency control (referenceId), ensuring financial integrity under high concurrency.

Visit bet.emanuelvini.dev View on GitHub

Distributed Locks

Redis + Atomic Ops

Financial Ledger

Integer Cents (No Float Bugs)

Real-time Broadcaster

SSE + Stateless API

Timeline

An evolution with auditable dates.

The public milestones below were checked against GitHub on May 16, 2026. The infrastructure layer comes from the personal story; the repository layer is the verifiable proof.

Verify on GitHub

2020 / Age 10

Java, Minecraft, and self-directed learning

The pandemic became a lab. The entry point was pure Java, Minecraft plugins, .jar files, plugin.yml, and reading stack traces directly, with English and Russian used as tools to unlock documentation and forums.

Proof: Narrative foundation: the later public Java sequence shows that this origin became real code.

Public GitHub

2021 / Age 11

First public Java plugins

Repositories such as zSilk2 and zManutencao appear on GitHub on June 21, 2021, focused on Bukkit/Spigot and server customization.

Proof: zManutencao: public initial commit on June 21, 2021; zSilk2: Java repository created the same day.

zManutencao

2022-2023 / Ages 12-13

Plugins, APIs, and server architecture

The JVM phase evolved into core modules, Minecraft/Discord linking, multi-server APIs, and plugins with specific rules for real communities.

Proof: zDiscordCore was created on April 30, 2022; MultiServer-API had commits on July 15, 2023 and August 19, 2023.

MultiServer-API

2023 / Age 13

Kotlin, SQL, and commercial automation

The stack expanded into Kotlin, relational databases, and Discord bots, connecting shop logic, communities, and data persistence.

Proof: AdvancedSQL, written in Kotlin, had public commits on September 1, 2023; ComuniMineBot was published on August 16, 2023.

AdvancedSQL

2026 / Age 16

Full-stack web products

The backend foundation moved into demonstrable applications with Next.js, Prisma, PostgreSQL, authentication, dashboards, uploads, metrics, and developer tools.

Proof: MTX-Upload, money-manager, TypeDash, SnippetVault, and apiFlash were created in March 2026.

typedash

Present

Transactional systems and AI agents

The current focus combines product engineering, financial consistency, polished interfaces, and AI orchestration to accelerate delivery without abandoning fundamentals.

Proof: Transactional Wallet Ledger was created on May 7, 2026; Tunelay appears as the newest repository on May 15, 2026.

transactional-wallet-ledger

Proof of Work

The public signals behind the narrative.

Pulled directly from the public GitHub API on May 16, 2026, separating original repositories from forks to map the real evolution by language and period.

original repos

Original public repositories, separated from forks, showing continuity from 2021 to 2026.

before 2024

Older original projects predating the current web product phase and the recent AI hype cycle.

public JVM repos

16 original Java repositories and 2 Kotlin repositories covering plugins, APIs, SQL, and server systems.

TypeScript repos

Modern layer with Next.js, dashboards, developer tools, metrics, and transactional systems.

What it means

The technical terms translated into real impact.

.jar, plugin.yml, and stack traces

This is not just “a Minecraft plugin”: it is Java packaging, build cycles, command/event declaration, and debugging real runtime errors.

Bare metal, VM, and zero overselling

This means operating physical resources responsibly: CPU, memory, disk, IPs, and bandwidth must match what was sold to the customer.

Pterodactyl, Nodes, and Eggs

This means provisioning game servers with isolation, runtime templates, port allocation, and networking, not merely installing a panel.

Webhooks and idempotency

This prevents a duplicated payment event from creating duplicated credit. Every financial event must be processed once and remain traceable.

Multi-agents and Vibecoding

This means using AI to accelerate analysis, boilerplate, tests, and iteration while keeping architecture and critical decisions under human control.

Stack

Seamless integration between interfaces, APIs, and data modeling.

The continuous project history shows a clear evolution: first Java/Kotlin and the JVM ecosystem, then TypeScript, Next.js, and web solutions with sophisticated business rules. The current highlight is Transactional Wallet Ledger: a monorepo architecture integrating Fastify and Next.js with a focus on auditability and transactional traceability.

Modern and reactive frontend employing App Router, React, Tailwind CSS, and Framer Motion.

High-performance backend supported by Fastify, Prisma, PostgreSQL, and strict authentication and validation control.

Production-grade repositories demonstrating advanced software engineering practices.

Selected projects

Strong projects for technical evaluation.

A technical curation of repositories maintained under emanuelVINI01, preserving the Java/Kotlin journey while prioritizing current systems, data-driven applications, and developer infrastructure.

View all

Full Stack2026

/ledger/atomic-tx

My Bet

Robust iGaming platform featuring 13 games, an idempotent financial ledger, and 8 PIX integrations.

TransactionalAuthReal-TimeSpeed Optimized

Next.jsNextAuthPrismaRedisSSE

View project

bet.emanuelvini.dev GitHub

React & AI2026

mcp://active-tab

Browia

Browser extension with an autonomous AI agent operating via MCP.

AIBrowser ExtensionOpen SourceTypeScript

TypeScriptReactManifest V3MCPOllama

View project

GitHub

Full Stack2026

/vault/public

SnippetVault

Full-stack case study for organizing technical knowledge.

AuthSearchOpen SourceTypeScript

Next.jsPrismaNextAuthZodTypeScript

View project

snippetvault.emanuelvini.dev GitHub