The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Back to feedPost
Security in motion and at rest — built in Python 🛡️
I built Sec-Toolkit, a two-layer security tool designed to keep data
safe everywhere it goes:
🔹In-Transit:
Verifies request signatures, validates user tokens, and checks web
security headers.
🔹At-Rest:
Encrypts sensitive files using AES and creates SHA-256 fingerprints
to ensure nothing has been tampered with.
It also includes automated checks using local AI, built with a clean
terminal interface for a smooth developer experience.
#Python | #CyberSecurity | #Coding
| #SoftwareEngineering | #DataProtection |#AppSec | #DevTools
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Related posts
B2B SaaS website design for Proof — an identity platform that lets AI agents act on behalf of real people, built to convert enterprise security buyers.
Proof issues cryptographically verified credentials: a human verifies once, and their AI agent is then authorized to sign, notarize or transact for them. The site had to sell a category most buyers had never heard of — agent authorization — to security, compliance and engineering leads at banks, law firms and hospitals, and move them into a sales conversation instead of a bounce.
The hero says it in five words — "Verify one. Authorize for everything." — next to a live credential card, so an abstract protocol becomes something you can see in two seconds. The page alternates near-black, white and electric blue, and every switch marks a new argument: the risk, the mechanism, the network, the platform, the API. That rhythm keeps a 14-section B2B SaaS website scannable in a single scroll.
I built 20+ Lottie animations for the parts copy can't carry — credential signing, the authorization handshake, the global network map — kept light enough not to cost load time. For imagery I wrote a style recipe for AI generation (one lens, one lighting setup, one grade) so the finance, legal and healthcare scenes read as one commissioned shoot rather than stock AI. Technical buyers get a real code block with real API calls, because that section is what they scroll to find.
14+ sections, desktop and mobile designed separately, a component library, Lottie files ready for the dev team, and a written art-direction guide for generating new imagery in-brand.
Built a digital presence for Associated Engineers & Builders
I wanted this website to feel like an extension of the company itself. Organized, clear and made to last. The visual style takes ideas from blueprints engineering charts and technical papers while keeping everything simple and up to date.
I designed and developed the website around their 30+ years of work, bringing together their services, projects, history, and company story into one responsive experience.The aim was straightforward: change a construction company into a powerful modern online presence without losing its engineering roots.
Built from beginning to end. Concept, design, development and launch.
What do you think of the style😍 ?
The Single HAProxy Illusion: Why your "High Availability" ingress is actually a single point of failure.
Most engineering teams set up an HAProxy or Caddy instance in front of their application clusters, configure health checks across three backend nodes, and check "High Availability" off their architectural checklist.
Here is the cold operational reality: if you only have one load balancer node, you do not have High Availability. You just have a very sophisticated single point of failure.
When that single proxy VM suffers a kernel panic, an Out-Of-Memory (OOM) killer invocation, a hypervisor migration lock, or a failed configuration reload, your entire production platform goes dark. Your redundant backends are completely unreachable, and your clients see hard connection timeouts.
True ingress resilience requires architectural decoupling at Layer-3 and Layer-4: • Twin redundant edge gateways operating Virtual Router Redundancy Protocol (Keepalived VRRP) sharing a floating Virtual IP (VIP). • Sub-second heartbeats: if the master node stops responding for 1,000ms, the backup node claims the VIP with zero manual intervention. • Synchronized stick-tables: active-active or active-passive session state replication ensuring client rate limits and session affinity survive node crashes. • Hitless socket reloads: leveraging modern Linux socket transfer mechanics (systemd socket activation or HAProxy master-worker mode) so zero TCP packets are dropped during updates.
Stop relying on single-node ingress illusions.
Explore our 1-week fixed-scope High-Availability Ingress & Hardened Reverse Proxies Sprint on Contra: https://contra.com/s/Ec6sEAUW-high-availability-ingress-and-hardened-reverse-proxies-ha-proxy-and-caddy
#DevOps #SRE #HAProxy #Infrastructure #Networking #HighAvailability #Linux
