Rasnex Lab
How we build
The engineering side of Rasnex: tools, rules and checks behind every project.
Stack
Web
HTML · CSS · TypeScript · Next.js · Astro · Cloudflare Workers
Mobile
Flutter · Dart · Swift · SwiftUI · Kotlin
Desktop
Swift · AppKit · C# · Python · Bash
Games & 3D
Unity · C# · WebGL · Blender pipeline
Back end
Node.js · Python · PostgreSQL · Supabase · R2 storage
AI
Claude · agent pipelines · image, voice, music and video models
Security
CSP · HSTS · secret scanning · encrypted backups · SPF/DKIM/DMARC
Blockchain
Solidity · EVM · wallet and exchange APIs
Rules
- Every release is checked by screenshots on desktop and phone, light and dark.
- Secrets live only on the server. Code is scanned for leaks before it is published.
- Source code is private; the public sees only the finished product.
- Backups are encrypted before they leave the machine, and restores are tested.
- Sign-in is never forced where the product works without it; account deletion is always available.
- A store rejection is fixed at the cause and turned into an automatic check for every product.
- Security testing only with the owner's written permission.
Encryption everywhere
HTTPS only, strict transport security, encrypted backups.
Secrets stay on the server
Keys never go into the app or the page. We scan code for leaks before each release.
Minimum data
We collect only what the product needs and say so plainly in the policy.
Global edge
Pages are served from the node closest to the visitor, with DDoS protection in front.
Several regions
Servers in different parts of the world, so one failure does not stop the service.
You own everything
Code, domains, accounts and data are handed over to you. No lock-in.
Report a vulnerability
Found a weakness in our site or product? Write to security@rasnex.com. We reply to every report and never pursue good-faith researchers.