<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Lobzytechnologiesltd on Medium]]></title>
        <description><![CDATA[Stories by Lobzytechnologiesltd on Medium]]></description>
        <link>https://medium.com/@lobzytechnologiesltd?source=rss-cbf81a755f7c------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*Oi53nn9NsrBnkrXl</url>
            <title>Stories by Lobzytechnologiesltd on Medium</title>
            <link>https://medium.com/@lobzytechnologiesltd?source=rss-cbf81a755f7c------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 20:43:39 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@lobzytechnologiesltd/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Why I Ditched Traditional Servers for a Serverless Telegram Neobank Backend]]></title>
            <link>https://medium.com/@lobzytechnologiesltd/why-i-ditched-traditional-servers-for-a-serverless-telegram-neobank-backend-7c35cdacaadc?source=rss-cbf81a755f7c------2</link>
            <guid isPermaLink="false">https://medium.com/p/7c35cdacaadc</guid>
            <category><![CDATA[serverless]]></category>
            <category><![CDATA[architecture]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[cloudflare]]></category>
            <category><![CDATA[fintech]]></category>
            <dc:creator><![CDATA[Lobzytechnologiesltd]]></dc:creator>
            <pubDate>Tue, 17 Nov 2026 18:47:33 GMT</pubDate>
            <atom:updated>2026-11-17T18:47:33.405Z</atom:updated>
            <content:encoded><![CDATA[<p>If you’ve ever built a fintech application, you know the infrastructure tax comes due long before your first user logs in.</p><p>Traditional architectures demand containerized instances, intricate VPC setups, and dedicated database clusters just to handle incoming API webhooks and request routing. For early-stage builders experimenting with conversational banking inside messaging apps like Telegram and WhatsApp, that heavy infrastructure overhead eats into margins before the product even has a chance to prove itself.</p><p>In modern systems design, shifting execution to the edge using serverless infrastructure changes the economics entirely. By leveraging edge workers, developers can build automated payment gateways, crypto routing logic, and virtual card handlers that run globally with zero server management — all for a monthly operating cost under $30.</p><p>Here is a breakdown of how the architecture works and how to approach it.</p><p>— -</p><p>### The Architectural Shift: Edge Routing vs. Monolithic Servers</p><p>When dealing with financial webhooks or Banking-as-a-Service (BaaS) integrations, your backend needs to validate payloads instantly, manage state securely, and route requests without latency spikes.</p><p>Traditional Node.js servers require constant monitoring, system patching, and manual scaling rules. In contrast, serverless edge runtimes handle incoming requests at data centers geographically closest to the user.</p><p>Below is an example of how an edge routing handler can process incoming platform webhooks cleanly in standard JavaScript:</p><p>```javascript<br>export default {<br> async fetch(request, env, ctx) {<br> if (request.method !== ‘POST’) {<br> return new Response(‘Method not allowed’, { status: 405 });<br> }</p><p>try {<br> const update = await request.json();<br> <br> // Parse incoming platform message payload<br> if (update.message) {<br> const chatId = update.message.chat.id;<br> const text = update.message.text;</p><p>// Route through banking gateway / intent parser<br> await processFinancialPayload(chatId, text, env);<br> }</p><p>return new Response(JSON.stringify({ status: ‘ok’ }), {<br> headers: { ‘Content-Type’: ‘application/json’ },<br> });<br> } catch (err) {<br> return new Response(JSON.stringify({ error: err.message }), {<br> status: 500,<br> headers: { ‘Content-Type’: ‘application/json’ },<br> });<br> }<br> },<br>};</p><p>async function processFinancialPayload(chatId, text, env) {<br> // Execute transaction routing or balance checks<br> console.log(`Routing transaction for chat ${chatId}`);<br>}</p><p>```</p><p>— -</p><p>### Bringing Conversational AI to Financial Workflows</p><p>Modern fintech users expect immediate, conversational interfaces. By embedding natural language intent parsing into the edge function, the system can interpret unstructured inputs — such as fund requests, balance checks, or asset conversions — and execute the correct underlying API calls dynamically.</p><p>Because this architecture relies on clean, modular JavaScript, the same core backend logic can be deployed across multiple messaging environments simultaneously. It serves as an adaptable boilerplate for localized fintech products, automated customer support portals, or community-driven finance tools.</p><p>— -</p><p>### Resource &amp; Implementation</p><p>For engineers looking to experiment with this edge architecture without building the boilerplate from scratch, the complete unencrypted starter framework — including the core worker script, dependency definitions (`package.json`), environment configuration templates (`wrangler.example.toml`), and documentation — is available for deployment.</p><p>👉 **[Access the Telegram Neobank Engine (Lite) Source Files](<a href="https://selar.com/996n91p97z)**">https://selar.com/996n91p97z)**</a></p><p>*Documentation for scaling into full-scale institutional setups with advanced compliance routing is included in the project package.*</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7c35cdacaadc" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to Route Cloudflare Workers Through a Static IP VPS (And Bypass API Whitelists)]]></title>
            <link>https://medium.com/@lobzytechnologiesltd/how-to-route-cloudflare-workers-through-a-static-ip-vps-and-bypass-api-whitelists-4a85c71e3c2a?source=rss-cbf81a755f7c------2</link>
            <guid isPermaLink="false">https://medium.com/p/4a85c71e3c2a</guid>
            <category><![CDATA[cloudflare]]></category>
            <category><![CDATA[security]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[nodejs]]></category>
            <dc:creator><![CDATA[Lobzytechnologiesltd]]></dc:creator>
            <pubDate>Sat, 14 Nov 2026 17:26:02 GMT</pubDate>
            <atom:updated>2026-11-14T17:26:02.186Z</atom:updated>
            <content:encoded><![CDATA[<p>If you’ve ever tried to integrate financial APIs, banking ledgers, or strict payment gateways directly inside a serverless **Cloudflare Worker**, you’ve likely hit a brick wall: **Dynamic IP Whitelists.**</p><p>Cloudflare uses a rotating pool of edge IPs. Traditional banking and fintech APIs that require a static IP whitelist will instantly reject your outgoing requests with a `403 Forbidden` error.</p><p>The traditional “fix” Cloudflare offers? Upgrade to **Cloudflare Enterprise** at $2,000+/month. That is completely out of reach for indie hackers and growing engineering teams.</p><p>— -</p><p>### The Solution: The Zero-Trust VPS Proxy Architecture</p><p>Instead of paying enterprise fees, you can route your Cloudflare Worker requests through a dedicated $5/month VPS running a secure reverse proxy.</p><p>**The Data Flow:**</p><ol><li>**The Trigger:** Your Cloudflare Worker needs to make a secure API call.</li></ol><p>2. **The Encrypted Tunnel:** The Worker sends an authenticated payload to your dedicated VPS static IP via HTTPS.</p><p>3. **The Static Gateway:** Your VPS (running a lightweight proxy) catches the payload, attaches your whitelisted static IP headers, and forwards it to the destination API.</p><p>4. **The Response:** The API sees a clean, consistent static IP and returns the data successfully.</p><p>— -</p><p>### Implementation Breakdown</p><p>#### 1. The Caddy + HTTPS Reverse Proxy Config (`Caddyfile`)</p><p>```text</p><p>your-proxy-domain.com {</p><p>reverse_proxy localhost:3000 {</p><p>header_up X-Forwarded-For {remote_host}</p><p>}</p><p>}</p><p>2. The Node.js Core Handler (server.js)</p><p>const express = require(‘express’);</p><p>const axios = require(‘axios’);</p><p>const app = express();</p><p>app.use(express.json());</p><p>app.post(‘/proxy-request’, async (req, res) =&gt; {</p><p>const authHeader = req.headers[‘authorization’];</p><p>if (authHeader !== `Bearer ${process.env.SECRET_TOKEN}`) {</p><p>return res.status(401).json({ error: ‘Unauthorized gateway access’ });</p><p>}</p><p>try {</p><p>const apiResponse = await axios({</p><p>method: req.body.method,</p><p>url: req.body.targetUrl,</p><p>data: req.body.payload,</p><p>headers: req.body.headers || {}</p><p>});</p><p>return res.status(200).json(apiResponse.data);</p><p>} catch (err) {</p><p>return res.status(500).json({ error: err.message });</p><p>}</p><p>});</p><p>app.listen(3000, () =&gt; console.log(‘Static IP Proxy active on port 3000’));</p><p>3. Systemd Auto-Restart Daemon (/etc/systemd/system/vps-proxy.service)</p><p>[Unit]</p><p>Description=Cloudflare Static IP VPS Proxy</p><p>After=network.target</p><p>[Service]</p><p>ExecStart=/usr/bin/node /opt/proxy/server.js</p><p>Restart=always</p><p>User=root</p><p>Environment=NODE_ENV=production</p><p>[Install]</p><p>WantedBy=multi-user.target</p><p>Get the Complete Production Blueprint</p><p>If you want to skip hours of trial-and-error, security hardening, and edge-case debugging, I have packaged this entire architecture into a comprehensive, production-ready 16-page technical blueprint.</p><p>It includes complete copy-pasteable scripts, security hardening guides, and step-by-step zero-trust configurations.</p><p>[👉 Get the Full 16-Page Blueprint on Gumroad ($100)](https://lobzytech.gumroad.com/l/cloudflare-static-ip)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4a85c71e3c2a" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>