Secure by default
Protection against forged form submissions, an application firewall, security headers and sessions that can be signed out on every device.
Inside vene.win
This site is built with Rullst.
vene.win runs on Rullst, the Rust web framework created by Tio Vené. It brings together everything a site needs to be fast and light, with its security protections on from day one.
Bit
Hi! I'm Bit, Tio Vené's robot. Click me for a tip!
- Hi! I'm Bit, Tio Vené's robot. Click me for a tip!
- In private lessons, every student gets their own plan: from the first game to the first olympiad.
- Want to make your own game? You can start without knowing how to code: we learn by doing.
- A little practice every week beats one all-nighter before the contest. Small bits make big programs!
- ACSL has four logic and programming contests per season, and Tio Vené runs study groups for Brazil.
- Before you register for a competition, always check the official website: dates can change.
Rullst 13
What Rullst brings to this site
Three checked languages
If a text is missing in Portuguese, English or Spanish, the site won't even compile. Plurals and dates follow each language's rules.
Database and migrations
Models, queries and migrations live in the code itself, on top of this site's SQLite database.
Ready-made admin
Nexus manages courses, lessons, students and lesson requests without writing admin screens.
Light and efficient
A single Rust program, with no separate application server, that uses little memory and responds quickly.
Assisted upgrades
cargo rullst upgrade shows what changes in the code before updating the framework, as in this site's move to version 13.
Rullst Green
Rullst Green: this site's measurements
The cargo rullst green command measures the app itself: size, memory, dependencies and the processor time spent per page. Each panel shows where the measurement was taken.
Windows · x86_64development computer
📦 Program size
16.0 MB
🚀 Pages served in the test
20,270
🧩 Dependencies
436
Measured on November 7, 2026 with cargo rullst 13.0.0-alpha.4, on the release binary (Windows, x86_64). The production server (Linux ARM64) may show slightly different numbers.
Load test: 10 seconds, 4 simultaneous connections requesting the home page, 0 errors.
Idle memory and processor time per page are only measured on Linux (green uses the system's /proc).
Linux · x86_64GitHub Actions Linux server
📦 Program size
15.6 MB
🧠 Idle memory
14.7 MB
⚡ CPU per page
0.23 ms
🚀 Pages served in the test
70,217
🧩 Dependencies
436
Measured on November 7, 2026 with cargo rullst 13.0.0-alpha.4, on the release binary (Linux, x86_64). The production server (Linux ARM64) may show slightly different numbers.
Load test: 10 seconds, 4 simultaneous connections requesting the home page, 0 errors.
Page weight
How much the home page weighs
What a browser with nothing cached receives over the network when it opens the home page, already compressed. Fewer bytes means less energy spent on the network and on the visitor's device.
vene.winNovember 8, 2026
📦 on a first visit, with styles, scripts and images
44 KB
🔁 on later visits (the rest stays cached on the device)
8 KB
🧩 of styles and scripts, compressed
29 KB
🚫 third-party scripts, trackers or ads
0
Measured on November 8, 2026 with scripts/medir-pagina-inicial.py: it requests the home page and every file it uses, as a browser with nothing cached does, and adds up the bytes that come over the network, without decompressing. GitHub measures again after every deploy and warns when the number changes by more than 5%.
Efficient software
Why a light site uses less energy
- The energy a server uses follows the processor time and memory the program needs. Less CPU and memory per page means more visits served by the same server, or a smaller server for the same site.
- Rullst is written in Rust and becomes a single compiled program, with no interpreter or virtual machine running underneath. That tends to use less CPU and memory than interpreted platforms or heavier frameworks.
- Studies comparing languages placed Rust among the most energy-efficient; more recent research shows that what really matters is each program's execution time. That is why vene.win measures itself with Rullst Green instead of making promises.
So we prefer to say “efficient software”, with numbers, rather than use generic labels like “eco-friendly” or “sustainable”: environmental claims like these must be substantiated, as required by CONAR in Brazil and Directive (EU) 2024/825 in Europe.
Sources: Pereira et al., 2017 ↗ · van Kempen et al., 2024 ↗ · Green Software Foundation ↗
Carbon estimate (SCI)
How much carbon this site's processing emits
With the processor time measured by Rullst Green and two sourced figures, the server processor's power and the carbon intensity of Brazil's power grid, we can estimate the carbon of each page with the SCI (Software Carbon Intensity) method, the ISO/IEC 21031:2024 standard. The server is in Brazil, on the National Interconnected System, a low-carbon grid where most of the power comes from renewable sources.
SCI · ISO/IEC 21031:2024estimate
🌱 CO₂e per million pages
≈ 5.9 mg
⚡ CPU energy per million pages
≈ 0.13 Wh
🔌 Power per busy core
2.01 W
🌎 Brazil's power grid (2025)
46.1 g/kWh
Formula: SCI = (E × I + M) ÷ R. E, the energy, is the measured processor time (0.23 ms per page, Linux x86_64, on November 7, 2026) × 2.01 W per busy core; I is the grid's carbon intensity (46.1 g of CO₂ per kWh, 2025 average); M, hardware manufacturing, is left out; R is one page served.
What this estimate leaves out
- The server running all the time: idle power, memory, disk and data-center cooling. The figure covers only the processor work to build each page.
- The network, Cloudflare and the visitor's phone or computer, which also use energy and are not counted.
- Hardware manufacturing (the M in the formula) and gases other than CO₂: the MCTI factor measures CO₂ from power generation. SCI uses the local grid average, with no discount for renewable-energy contracts or certificates.
- The processor time was measured on the GitHub Actions Linux server (x86_64), not on the production server (Linux ARM64), and the power per core comes from the manufacturer's spec sheet, not an energy meter. These are approximations.
So this site's environmental claim is this, and only this: an SCI estimate of about 5.9 mg of CO₂e per million pages, counting only the app's processing. We don't call the site “green”, “carbon neutral” or “sustainable”: that would require measuring the full life cycle and proving it.
Sources: SCI, Green Software Foundation ↗ · ISO/IEC 21031:2024 ↗ · MCTI (Brazil): grid emission factors ↗ · Ampere: Altra product brief ↗ · Oracle Cloud: A1 shapes ↗ · cargo rullst green ↗
Learn
Want to build sites like this?
In private lessons you can learn web programming with Rust and Rullst, from the first project to a live site.