DEV Community: @venelouis

I just created the best web FullStack framework in Rust language: the Rullst!

@venelouis — Wed, 27 May 2026 22:15:30 +0000

Rullst - 📜🦀🌐🤖🚀

"Rust for those who want to build, not suffer."

📖 See all the changes in our Changelog!

📚 Read the Official Documentation!

📦 View on Crates.io!

Be a contributor to help us build the best web framework on the internet. 🦀❤️

Rullst (Rust + Fullstack) is an opinionated, developer-first full-stack web framework for Rust, obsessively designed for Emotional Productivity.

It was created to solve the biggest problem in the Rust web ecosystem: the high barrier of entry that turns web programming into a PhD research on compiler design. We believe you should spend your energy building your business, not fighting borrow checkers and manual routing setups.

💡 The Rullst Manifesto

"Most Rust frameworks treat the web developer like a compiler engineer. Rullst treats the developer like someone who wants to build awesome products at lightning speed."

In the current ecosystem, to write a simple CRUD, you are forced to glue dozens of crates together, manually map nested routing trees, write verbose ORMs requiring multiple structs, and continuously clone variables inside dynamic HTML templates just to satisfy the borrow checker.

Rullst redefines this experience. We offer an integrated, cohesive developer experience that brings the sweetness and iteration speed of Laravel and Next.js together with the Formula 1 performance and military-grade safety of Rust, Axum, and Hyper:

No More Frankenstein setups: A single cohesive framework managing your server (Axum), your database (rust-eloquent), and your HTML rendering.
No More Borrow Checker fights in UI: Our compile-time JSX-like html! macro processes pure elements on the server (SSR). It generates optimized string-builders directly at compile time. It's blazing fast, safe, and SEO-friendly by default.
First-Class Active Record ORM: Native integration with your rust-eloquent package. Interacting with databases is as intuitive as user.save().
AI-Native Engineering & AI-Friendly: Designed from the ground up for modern pair-programming. Strict type-safety, zero dynamic runtime magic, automatic .ai-rules scaffolding, and structured schemas prevent AI agent hallucinations and allow instant compiler self-correction.

🏆 Everything You Need, Built-In

Rullst ships with 8 completed milestones covering every layer of modern web development:

Category	Features
🛠️ CLI & DX	`cargo rullst new` wizard, `make:controller`, `make:model -m`, `make:middleware`, `make:worker`, `generate:openapi`, `cargo rullst upgrade` (self-healing)
🗄️ Database	Active Record ORM, Migrations (`db:migrate`, `db:rollback`, `db:status`), Seeders & Factories, HasMany / BelongsTo / BelongsToMany, Eager Loading
🔒 Auth & Security	Argon2 hashing, JWT & Cookie sessions, CSRF protection, Social OAuth (Google, GitHub, Facebook, Twitter via `rust-socialite`), `cargo rullst auth` scaffolding
⚡ Frontend	HTMX first-class support, TailwindCSS auto-integration, partial template rendering, Rullst Live (Phoenix LiveView-inspired server-driven UI), Wasm Islands (`#[client_component]`)
📦 Production	Queue (SQLite/Redis), Cache (Memory/Redis), Task Scheduler (Cron), Docker multi-stage builds, Rullst Horizon dashboard
🏢 Enterprise	Declarative Validation, Mailer (SMTP/Resend/SendGrid), Storage (Local/S3/R2), WebSockets, Multi-Tenancy, Feature Flags, E2E Testing
🚀 Unfair Advantage	AI Core (`rullst::ai` — OpenAI/Gemini/Anthropic/Ollama + RAG), Rullst Studio (visual DB GUI), Self-Healing Error Console (AI auto-fix), Hot Reloading via `dylib`
🌍 Edge & Data	Edge Runtime (Cloudflare Workers, Fastly, AWS Lambda@Edge), Zero-Config Distributed SQLite Replication (Turso/D1), Autonomous Upgrades

🎨 The "Hello World" That Conquers at First Sight

This is a complete, fully operational web server with type-safe routing, compile-time HTML rendering, and automatic XSS escaping. It is exactly 20 lines of code:

use rullst::{html, routes, Server, Router, response::{Html, IntoResponse}};

async fn hello() -> impl IntoResponse {
    Html(html! {
        <main style="display: grid; place-items: center; height: 100vh; background: #090d16; color: #fff; font-family: system-ui;">
            <div style="text-align: center;">
                <h1 style="font-size: 4rem; margin: 0; background: linear-gradient(135deg, #00f2fe, #4facfe); -webkit-background-clip: text; -webkit-text-fill-color: transparent;">
                    "Hello, World!"
                </h1>
                <p style="color: #64748b; font-size: 1.25rem; margin-top: 1rem;">
                    "Written in Rust. Rendered in microseconds. Safe by default."
                </p>
            </div>
        </main>
    })
}

#[tokio::main]
async fn main() -> Result<(), Box<dyn std::error::Error>> {
    Server::new(routes![get("/" => hello)])
        .run(3000)
        .await?;
    Ok(())
}

⚡ Get Started in 10 Seconds

Scaffold a fully operational application with our interactive CLI wizard!

# 1. Run the interactive CLI scaffolding tool
cargo rullst new

# The wizard will prompt you:
# 🚀 App name? (no spaces allowed) -> my-app
# 🏗️ What would you like to build? -> Full-Stack Web App (SaaS, Portfolio, Blog) / REST API
# 🔥 Enable Hot Reloading by default? -> Yes / No
# 🗄️ Will your project need a Data Base? -> Yes / No
# 💾 Select a DB Provider -> Sqlite / Postgres / MySQL/MariaDB

# 2. Enter the project folder
cd my-app

# 3. Start your high-performance full-stack app immediately!
cargo run

# 🔥 Or enable instant Hot Reloading (no server restart!):
HOT_RELOAD=1 cargo run

🛠️ The Full-Stack Active Record Experience

When your application grows, Rullst scales with you using Active Record:

use rullst::{html, routes, Server, Router, response::{Html, IntoResponse}};
use rust_eloquent::{Eloquent, EloquentModel, sqlx::{self, FromRow}};

#[derive(Debug, Clone, FromRow, rust_eloquent::Eloquent)]
#[eloquent(table = "users")]
pub struct User {
    pub id: i32,
    pub name: String,
}

async fn home() -> impl IntoResponse {
    // Elegant, type-safe data fetching
    let users = User::all().await.unwrap();

    Html(html! {
        <div style="background: #0f172a; color: #fff; padding: 5rem; text-align: center; font-family: sans-serif;">
            <h1>"Total Active Users: " {users.len()}</h1>
        </div>
    })
}

// 1. Declare the artisan macro here to intercept CLI arguments for migrations
rullst::artisan!();

#[tokio::main]
async fn main() -> Result<(), Box<dyn std::error::Error>> {
    // 2. The artisan! macro automatically intercepts `db:*` commands and exits early.
    // If it's a normal run, it continues server execution here.

    let router = routes![
        get("/" => home),
    ];

    Server::new(router)
        .run(3000)
        .await?;

    Ok(())
}

🗄️ Database Migrations (Artisan CLI)

Rullst includes an embedded, high-performance migration runner. You don't need external binaries. The framework ships with a CLI tool that parses pure Rust closures to construct your schema safely.

# Scaffold a new migration using pure Rust DSL
cargo rullst make:migration create_users_table

# Run all pending migrations against your database
cargo rullst db:migrate

# Rollback the last batch of migrations
cargo rullst db:rollback

Under the hood, these commands are intercepted by the rullst::artisan!() macro, guaranteeing the server never starts when you only want to migrate your database.

🛡️ Self-Healing Upgrades

Afraid of breaking changes when upgrading the framework? Don't be. Rullst was built with a "Self-Healing Upgrades" philosophy.

When a new version of Rullst introduces API changes, we never break your code immediately. Instead, we use #[deprecated] warnings. You can update your entire application automatically using our CLI:

cargo rullst upgrade

This command will safely update the Rullst dependency and use Rust's powerful cargo fix refactoring tools to automatically rewrite your code to match the new API signatures. Stress-free upgrades, forever.

🔥 Hot Reloading (Zero Downtime Dev Loop)

Rullst supports Hot Reloading via Dynamic Linking — change your routes, handlers, and templates, and see the changes reflected instantly without restarting the server or losing connections:

# Start your app in hot-reload mode
HOT_RELOAD=1 cargo run

# ⚡ Edit any handler in src/ → Rullst detects the change
# 🔄 Background recompilation of the cdylib
# 🚀 Router hot-swapped atomically — zero downtime!

Under the hood, Rullst compiles your routes as a dynamic library (cdylib), loads it via libloading, and uses a notify file-watcher to detect changes and trigger background rebuilds. The router is swapped atomically via Arc<RwLock<Router>> — the HTTP server never restarts and TCP connections are never dropped.

🎯 Architecture under the hood

Rullst is structured as a modular monorepo Cargo Workspace to optimize compile times:

rullst (Core Crate): Wraps and configures Axum, handles life-cycle DB injection, and exposes response types. Ships with production utilities (Queue, Cache, Scheduler), enterprise features (Validation, Mailer, Storage, WebSockets, Horizon), AI-Native core (rullst::ai), Rullst Live (server-driven UI), Wasm Islands, and Hot Reloading via dynamic linking.
rullst-macros (Compiler-Engine): Procedural JSX-like compiler that outputs safe memory-buffer string extensions at compile time.
cargo-rullst (CLI Scaffold): Scaffolds clean, isolated local-linked workspaces that compile out-of-the-box.

For detailed technical conventions, directory structures, and framework APIs, refer to our Official Specification (SST).

📝 License

Distributed under the MIT License. See LICENSE for more details.

rust #rullst

A jornada natural de um webapp:

@venelouis — Wed, 29 Apr 2026 03:42:22 +0000

A jornada natural de um webapp:

Fase 1 — Início VPS simples, LEMP ou Docker
(0–50k usuários/mês) R$26–70/mês

Fase 2 — Crescimento VPS maior + Docker Compose
(50k–300k usuários/mês) R$50–150/mês

Fase 3 — Escala Cloud + Docker + Container orchestration
(300k–1M usuários/mês) R$300–1.000+/mês
(Azure Container Apps, AWS ECS, Google Cloud Run)

Fase 4 — Grande escala Kubernetes (K8s) na Cloud
(1M+ usuários/mês) R$2.000+/mês
(AKS, EKS, GKE)

Créditos acabam mais rápido com muitos usuários no Azure Cloud?
Não! E esse é um ponto muito importante sobre App Service e MySQL Flexible:

App Service B1 → cobra por HORA rodando = $13/mês fixo
MySQL B1ms → cobra por HORA rodando = $12/mês fixo
10 usuários/dia → $25/mês
10.000 usuários/dia → $25/mês ← IGUAL!
Os custos SÓ aumentam se você escalar manualmente (mudar para B2, B3, etc.) ou se o armazenamento do MySQL ultrapassar 20GB. Para um site de comunidade de estudos, isso não vai acontecer tão cedo.

Os $100 duram ~4 meses independente do tráfego. 🎉

MySQL → Docker? Trivial! ✅ Sim, é a coisa mais simples. O workflow completo no futuro (Hetzner VPS):

bash

1. Exportar da Azure (ou Hostinger)

mysqldump -h host -u usuario -p cosmos_scriptura > backup.sql

2. Subir Docker na VPS com MySQL incluído

docker compose up -d

3. Importar o banco no container Docker

docker exec -i cosmos_db mysql -u cosmos_admin -p cosmos_scriptura < backup.sql

Pronto! ✅

E o docker-compose.yml na VPS ficaria assim (adicionamos um serviço db):

yaml
services:
app:
# Laravel (já existe)
db:
image: mysql:8.0
volumes:
- mysql_data:/var/lib/mysql # dados persistem entre restarts
environment:
MYSQL_DATABASE: ***
MYSQL_ROOT_PASSWORD: senha_forte
volumes:
mysql_data: # volume persistente

Quantos usuários uma VPS aguenta?

Depende do que o site faz — mas para um webapp Laravel de comunidade/estudos como o seu:

VPS RAM/CPU Usuários simultâneos Usuários ativos/dia Usuários/mês
Hetzner CX23 (R$26) 2 vCPU / 4GB 50–150 ~5.000 ~100.000
Hetzner CX33 (R$51) 4 vCPU / 8GB 150–400 ~15.000 ~300.000
DO 2GB (R$69) 1 vCPU / 2GB 30–100 ~3.000 ~60.000
NOTE

Esses números assumem OPcache ativado no PHP (acelera 3–5x), Nginx como servidor web e queries MySQL bem otimizadas. Sem OPcache, divide por 3.

Quando a VPS começa a sofrer:

CPU > 80% constantemente
Tempo de resposta > 2 segundos
Erros 502/504 frequentes nos horários de pico

Quando migrar da VPS para Cloud? Não é só sobre número de usuários — é sobre o que você precisa:

VPS é suficiente enquanto:
✅ < 500 usuários simultâneos
✅ Um servidor aguenta o pico
✅ Queda de 30 min/mês é aceitável
✅ Você faz backup manual
Hora de ir para Cloud quando:
❌ Picos imprevisíveis de tráfego (ex: viral nas redes sociais)
❌ Precisa de 99.9%+ de uptime (SLA garantido)
❌ Usuários em múltiplos países (latência)
❌ Time cresceu e deploy manual virou risco
❌ Dados críticos precisam de backup automático e compliance

Em números práticos para o seu app:

Hoje → ??? usuários → VPS Hetzner R$26/mês ✅
100k+ usuários/mês → VPS maior ou Cloud básica
500k+ usuários/mês → Cloud com auto-scaling

Na Cloud com muitos usuários — usar Docker também? Sim, e aí o Docker vira essencial, não opcional. É a diferença entre escalar manualmente e escalar automaticamente:

SEM Docker na Cloud (tradicional):
Tráfego dobra → você acorda às 3h → sobe servidor maior → reza

COM Docker na Cloud (moderno):
Tráfego dobra → Cloud sobe 2 containers automaticamente → você dorme

Aqui está uma comparação realista para quando você tiver usuários pagantes:

🔵 Continuar na Azure (Cloud Gerenciada)
Custo: ~R$ 1.500/ano (no plano básico).
Vantagem: Paz de espírito. Se o banco de dados cair, a Microsoft resolve. Se precisar de mais potência, você clica em um botão. O backup é automático.
Custo-benefício: Excelente se você tem usuários pagantes. O seu tempo vale mais do que R$ 120 por mês. Se você passar 2 horas por mês consertando um servidor que caiu, já "perdeu" dinheiro.

🐧 Mudar para uma VPS (Hetzner/DigitalOcean)
Custo: ~R$ 300/ano.
Vantagem: Economia pura. É 5x mais barato que a Azure.
Desvantagem: Trabalho manual. Você é o "zelador" do servidor. Você precisa configurar o firewall, renovar o SSL (HTTPS), garantir que o backup está funcionando e atualizar o Linux. Se o site cair às 3 da manhã, é você quem tem que entrar via SSH para descobrir o porquê.

Minha Opinião Sincera:
Fase 1 (Agora): Use os $100 de estudante da Azure. É grátis, é profissional e você aprende a usar uma ferramenta de ponta.
Fase 2 (Crédito acabou):
Se o site estiver dando lucro: Fique na Azure. A "tranquilidade" de um serviço gerenciado compensa o custo extra. Você foca em ganhar mais dinheiro com o site, não em mexer em terminal de Linux.
Se o site for um hobby ou o lucro for baixo: Mude para uma VPS (Hetzner). Com o Docker que já criamos, essa migração será muito rápida (questão de 1 hora).

Conclusão: Para quem tem usuários pagantes, a Cloud (Azure) costuma ter o melhor custo-benefício porque o risco de o site ficar fora do ar e você perder clientes é muito menor.

Curto Prazo (Agora): Azure ✅
Não tem nem o que pensar. Você tem $100 de graça. É a melhor nuvem do mundo enquanto você não está pagando por ela. Use esse tempo para aprender e validar seu site sem gastar um centavo.
Longo Prazo (Quando você tiver que pagar do bolso):
Se o seu público é brasileiro, a Azure é excelente porque o servidor no Brasil (Brazil South) é muito rápido e estável.

Porém, se eu fosse recomendar algo além da Azure, as melhores alternativas para o seu perfil (Laravel + Comunidade) seriam:

DigitalOcean (App Platform): 🥇 Minha recomendação número 1 pós-Azure. É muito mais simples de configurar que a Azure, o preço é fixo e transparente (você sabe exatamente quanto vai pagar), e eles amam o Laravel. É o equilíbrio perfeito entre a VPS barata e a Cloud complexa.

Google Cloud (GCP): Ótimo se você quiser usar o Cloud Run. O custo pode ser quase zero se você tiver pouco tráfego, mas o banco de dados (Cloud SQL) é caro.

AWS: É a maior de todas, mas é um "labirinto". Eu evitaria para um projeto solo, a menos que você queira muito aprender para o seu currículo.

Meu Veredito:
Fique na Azure agora para aproveitar os créditos. Se um dia você decidir que a Azure está cara ou complexa demais, mude para a DigitalOcean.

Dica de Ouro: O Laravel tem uma ferramenta oficial chamada Laravel Forge. Ela gerencia servidores para você (na DigitalOcean, Hetzner ou AWS). Se o seu site crescer e você quiser o preço baixo de uma VPS com a facilidade da Azure, o Forge é o caminho que 90% dos profissionais de Laravel usam.

Novo Cálculo (Azure for Students):
App Service (F1): $0.00 (Sempre gratuito).
MySQL Flexible Server (B1ms): $0.00 durante os primeiros 12 meses (A conta de estudante inclui 750 horas/mês gratuitas deste banco por um ano).
Crédito de $100: Como seu custo mensal será praticamente zero no primeiro ano, seus $100 dólares ficarão guardados!
Resultado:

Primeiros 12 meses: Custo $0. Você não gasta nada dos seus $100.
Após 12 meses: O banco passa a custar ~ $15/mês. Seus $100 começariam a ser usados então, durando mais uns 6 a 7 meses.
Total: Você consegue manter o projeto rodando por cerca de 18 meses (1 ano e meio) sem tirar um centavo do bolso!

Building the Impossible: How I Built Two Complex Platforms with PHP, Next.js, and AI

@venelouis — Sun, 26 Apr 2026 22:45:32 +0000

Many times, we have ideas that seem too big for our current skill set. For a long time, I dreamed of creating tools that merged technology, science, and ancient languages, but the technical complexity felt like an insurmountable barrier.

Recently, with the help of AI, I finally managed to launch two robust projects. I want to share the process and the tech stack I used to make it happen.

The Dream: Why were these projects "impossible" for me?

Even though I already knew how to code, building a gamified platform with the level of polish I envisioned required a depth of knowledge I hadn't fully mastered.

I knew that even if I could build it alone, the time investment and the "head-scratching" involved in debugging would be massive. AI changed the game by acting not just as a code generator, but as a partner that could fix bugs and suggest intelligent solutions to complex architectural problems. It made the development workflow much faster and more accessible.

Project 1: creio.eu (Gamified Learning)

creio.eu was born from a desire to unite scientific and biblical knowledge into a gamified environment.

Tech Stack:

Backend: Laravel (PHP)
Frontend: Blade / Tailwind CSS

https://creio.eu

*How AI helped me here:
*

Data Structuring: Organizing massive volumes of information into coherent Laravel migrations.
Gamification Logic: Designing the leveling system and user progress tracking.
Database Optimization: Fine-tuning queries for the quizzes to ensure high performance.

The Technical Challenge: biblia.creio.eu (Interlinear Bible)

This was my most ambitious project. Dealing with ancient languages like Hebrew, Aramaic, Ge'ez, and Armenian requires extreme technical precision.

Tech Stack:

Frontend: Next.js
Status: Open Source 🚀

https://biblia.creio.eu

The challenge of ancient scripts:

Working with different scripts—especially Right-to-Left (RTL) languages like Hebrew—and specific fonts was a constant hurdle. AI was fundamental for:
Interlinear Formatting: Correcting the alignment between multiple languages and writing directions.
Data Curation: I used AI to find public domain texts and open-source fonts, ensuring the project remained legally compliant and truly open.
Character Rendering: Solving encoding and font-rendering issues for Ge'ez and Armenian within Next.js components.

Open Source

I am a firm believer in free knowledge. Because of that, the code for the Interlinear Bible is open to the community:

cristianismohumilde / biblia.eu.creio

📜 Biblia.Creio.EU

Leia em português 🇧🇷

🏛️ Ancient Manuscripts | 🔍 Interlinear Study | 🚀 Static-First Architecture

Biblia.Creio.EU is a high-level open-source interlinear Bible study platform. Built with Next.js for high-performance static generation, it provides a professional tool for deep analysis of original manuscripts across multiple linguistic traditions.

🎯 Project Objectives

Biblia.Creio.EU provides a complete, academia-grade interlinear experience:

💎 Ancient Manuscript Witnesses: Hebrew, Aramaic, Greek, Latin, Ge'ez, Syriac, Coptic, and Armenian.
✍️ Curation-based Literal Translation: Word-for-word literal translations developed for structural fidelity.
📚 Multi-Language Lexicons: Comprehensive support for Strong (Hebrew/Greek), Jastrow (Aramaic), Dillmann (Ge'ez), LSJ, L&S, and more.
⚖️ Multi-traditional Comparison: Simultaneous analysis across key linguistic witnesses of biblical history.

🛡️ Legal Compliance & Transparency

This project is a pillar of Open Data. We ensure absolute legal safety for contributors and users:

🔓 Public Domain: All linguistic databases (lemmas, morphology, and base dictionaries) use…

View on GitHub

My Workflow with AI

To bring these ideas to life, I used a mix of tools. I started with GitHub Copilot Student until I hit my token limits, and then moved to Antigravity, which proved to be an excellent resource.

A story from the trenches: At one point, the Aramaic fonts simply wouldn't align with the translations. I fed the AI a detailed prompt describing my JSON structure and the expected CSS behavior. It suggested a flexbox solution combined with specific direction: rtl overrides that I hadn't considered, fixing the layout instantly.

Click to see the type of prompt I used for the font logic
"I need to render an interlinear text where the top line is Hebrew (RTL) and the bottom is English (LTR). How can I structure my Next.js components so the word-mapping remains visually synchronized even on responsive screens?"

Conclusion: The Future of Development

Without these tools, I would still be in the "what if..." phase. Today, both sites are live. AI doesn't replace the creator, but it certainly gives wings to those who want to build something new by removing the "fear" of technical barriers.

Let’s Talk!
I’d love to know: do you have a project that only exists because of AI? Or do you think we are becoming too dependent on these tools?

Leave a comment below, let's exchange experiences!

Since it's Open Source, I use the Liquid tag to invite contributors:
Contribute on GitHub!

No future without sustainability

@venelouis — Wed, 12 Mar 2025 02:01:53 +0000

This is a submission for the Future Writing Challenge: How Technology Is Changing Things.

Dear Family and Friends,

Technology is changing our world at lightning speed, and I wanted to share some thoughts on what we can expect in the coming years.

The Rise of Artificial Intelligence (AI)

Remember when getting information meant going to the library and flipping through dusty books? Now, we can ask an AI chatbot almost anything! Imagine AI as a super-smart friend who knows the answer to almost every question. But just like a friend, sometimes they need our help to get things right. It's like having a robot that helps with homework, but we still need to think and learn to do it correctly!

AI is transforming how we learn and work. In the future, we might have personalized lessons and more creative jobs. However, we also need to learn how to use technology responsibly and ethically. AI can help solve complex problems like climate change and diseases, but we must be careful not to rely on it too much and lose our ability to think for ourselves.

Connectivity and Robotics

Connectivity is also evolving rapidly. Remember when we played "telephone" as kids? Now, we can talk to people on the other side of the world in real-time, seeing their faces on our phone screens! Robots are learning to do more and more, like self-driving cars and machines that help care for the sick.

Technology is changing how we communicate, have fun, and connect with each other. Social media connects us with people worldwide but can also make us feel isolated and anxious. Automation is changing the job market, creating new opportunities and challenges. We need to prepare for the jobs of the future by learning new skills and adapting to change.

The Importance of Sustainability

We must take care of our planet so that all animals and people can live happily and healthily. Technology can help us create new things without polluting the air and water. It's like using recycled materials to build cool new toys without cutting down more trees or littering.

Sustainable technology is essential for ensuring a better future for everyone. We need to invest in renewable energy, biodegradable materials, and technologies that reduce our environmental impact. Technology can help us monitor and protect the environment, creating early warning systems for natural disasters and solutions for pollution.

A Message of Hope and Optimism

The future of technology can be amazing! We can create incredible things that will help people and the planet. But we must use technology wisely and take care of each other. Together, we can build a better world with the help of technology!

Technology has the potential to transform the world for the better, creating innovative solutions to the challenges we face. But we need to work together to ensure that technology is used ethically and responsibly. I believe that with the help of technology, we can build a more just, sustainable, and happy future for all.

I hope this gives you a glimpse into the exciting and rapidly changing world of technology. I'm excited to see what the future holds!

Warmly,

Venelouis T. S. Palhano

Additional Prize Categories

Explain Like I'm Five and Ripple Effects

Most Known Penetration Testing Linux distributions

@venelouis — Fri, 30 Aug 2024 11:20:47 +0000

Several #Linux distributions include numerous penetration testing tools. 🛠️

These are just some of the most popular ones. Do you agree? Make a comment below.

To learn more about penetration testing, check out the #SkillsForAll Free Cisco course on ethical hacking! 💻

👉 http://cs.co/6049mdRaN

Sharing MLH Survey (chances to win a brand new laptop)!

@venelouis — Fri, 17 May 2024 23:28:08 +0000

Sharing MLH Survey (chances to win a brand new laptop)! It doesn't even matter if you don't know MLH! Participe and have a chance! Major League Hacking #MLH #MajorLeagueHacking #Survey

https://hackp.ac/community-census-s2024

I got a testimonial on Exercism

@venelouis — Mon, 13 May 2024 23:41:39 +0000

https://exercism.org/profiles/venelouis/testimonials?uuid=daef1645-d5ac-462c-89d7-ba3d6609dee8