<?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"><channel><title><![CDATA[OrbixPanel]]></title><description><![CDATA[Engineering insights, DevOps tutorials, and self-hosting guides for OrbixPanel—the Go, NestJS, and React web hosting panel with Vercel-style Git deploys.]]></description><link>https://orbixpanel.hashnode.dev</link><image><url>https://cdn.hashnode.com/uploads/logos/6af1a897a83903c56a041dec/a6e19a79-22ec-47c8-bafc-429881efc6bf.png</url><title>OrbixPanel</title><link>https://orbixpanel.hashnode.dev</link></image><generator>RSS for Node</generator><lastBuildDate>Sat, 21 Nov 2026 17:05:56 GMT</lastBuildDate><atom:link href="https://orbixpanel.hashnode.dev/rss.xml" rel="self" type="application/rss+xml"/><language><![CDATA[en]]></language><ttl>60</ttl><item><title><![CDATA[How We Designed OrbixPanel for Security: Zero-Token OAuth, AES Encryption, and Isolated Runtimes]]></title><description><![CDATA[Explore the OrbixPanel v1.1 Security Whitepaper: AES-256-GCM secret vaults, unprivileged systemd app sandboxing, zero-token OAuth, and local AI guardrails.]]></description><link>https://orbixpanel.hashnode.dev/how-we-designed-orbixpanel-for-security-zero-token-oauth-aes-encryption-and-isolated-runtimes</link><guid isPermaLink="true">https://orbixpanel.hashnode.dev/how-we-designed-orbixpanel-for-security-zero-token-oauth-aes-encryption-and-isolated-runtimes</guid><category><![CDATA[Devops]]></category><category><![CDATA[Security]]></category><category><![CDATA[#selfhosted]]></category><category><![CDATA[golang]]></category><dc:creator><![CDATA[Maksudul Islam]]></dc:creator><pubDate>Sun, 15 Nov 2026 10:57:38 GMT</pubDate><enclosure url="https://cdn.hashnode.com/uploads/covers/6af1a897a83903c56a041dec/d923f132-6611-4157-9a8a-f2f4264c07c1.jpg" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>When building a self-hosted server control panel, security isn't just a checklist—it is the foundational architecture.</p>
<p>If you are hosting production workloads, databases, and customer sites on your own infrastructure using <strong>OrbixPanel</strong> (our Go, NestJS, and React web hosting platform), you need total clarity on how your system boundaries are enforced, where your secrets live, and how applications are isolated.</p>
<p>Today, we are diving into our newly published <a href="https://orbixpanel.com/blog/orbixpanel-security-whitepaper"><strong>OrbixPanel Security Whitepaper (v1.1)</strong></a>. Here is a look at the core security principles powering the platform.</p>
<h2>🏗️ 1. The Shared Responsibility Model</h2>
<p>Because OrbixPanel is self-hosted directly on your VPS or dedicated server, your data, credentials, and customer workloads never leave infrastructure you control. There is no middle-tier proxy or external SaaS holding your keys.\</p>
<img src="https://cdn.hashnode.com/uploads/covers/6af1a897a83903c56a041dec/56bb0992-b8b9-4a13-bf4c-dfdb0a34a62b.png" alt="" style="display:block;margin:0 auto" />

<ul>
<li><strong>What OrbixPanel Secures:</strong> Session integrity (JWT/2FA), role-based access control (RBAC), database encryption of sensitive OAuth credentials, agent task scoping, and automated TLS lifecycle management.</li>
<li><strong>What You Secure:</strong> Host OS kernel patches, SSH access keys, firewall/security group rules, and your root master keys (<code>ENCRYPTION_KEY</code> and <code>JWT_SECRET</code>).</li>
</ul>
<h2>🔒 2. Secrets Management &amp; Zero-Token Git Sprawl</h2>
<p>One of the biggest risks in modern server management is plaintext credential leakage or third-party token relaying.</p>
<ul>
<li><strong>AES-256-GCM Vault:</strong> All sensitive recovery secrets—including OAuth client secrets, access tokens, and refresh tokens—are encrypted at rest using <strong>AES-256-GCM</strong>.</li>
<li><strong>Per-Secret Salts &amp; IVs:</strong> A unique random 96-bit IV and a 128-bit salt are generated per secret, ensuring that identical plaintexts never yield identical ciphertexts.</li>
<li><strong>Direct Provider Exchange:</strong> When connecting GitHub, GitLab, or Bitbucket for 1-click deployments, the code-for-token exchange happens server-to-provider directly. <a href="http://OrbixPanel.com">OrbixPanel.com</a> is never in the path.</li>
</ul>
<h2>📦 3. Process &amp; Application Isolation</h2>
<p>To ensure that a compromised application or rogue script cannot compromise the host server, OrbixPanel enforces strict systemd sandboxing:</p>
<ul>
<li><strong>Non-Root Control Plane:</strong> The NestJS API control plane runs under a dedicated, unprivileged service account (<code>PrivateTmp=true</code>).</li>
<li><strong>Isolated Systemd Units:</strong> Every deployed application runs as its own unprivileged systemd unit (<code>www-data</code>) with strict fork-bomb guards, task caps, and tamper-evident journald logging.</li>
<li><strong>Resource Ceilings:</strong> Built-in cgroup enforcement (<code>MemoryHigh</code>/<code>MemoryMax</code> and <code>CPUQuota</code>) guarantees that a memory leak in one app triggers an OOM kill specifically for that unit rather than crashing the entire host.</li>
<li><strong>Filesystem &amp; Capability Hardening:</strong> App units execute with <code>NoNewPrivileges=true</code>, an empty capability set, read-only system paths (<code>ProtectSystem=full</code>), and private temporary directories (<code>PrivateTmp=true</code>).</li>
</ul>
<h2>🤖 4. AI Copilot Privacy &amp; Guardrails</h2>
<p>OrbixPanel features an optional native AI Copilot to help diagnose server incidents and read system logs.</p>
<ul>
<li><strong>100% Local Inference Support:</strong> By pointing the panel to a local model running via Ollama, all prompts, logs, and system metrics stay on your server with zero external API calls or telemetry.</li>
<li><strong>Diagnostic-First Design:</strong> The copilot recommends potential fixes by inspecting local metrics rather than executing autonomous, destructive root shell commands.</li>
</ul>
<h2>📄 Read the Full Whitepaper</h2>
<p>Security through obscurity is never a valid strategy. We believe in complete transparency about what our software does—and what is still on our roadmap.</p>
<p>You can read the complete, unedited <strong>OrbixPanel Security Whitepaper v1.1</strong> directly on our site: 👉 <a href="https://orbixpanel.com/blog/orbixpanel-security-whitepaper"><strong>orbixpanel.com/blog/orbixpanel-security-whitepaper</strong></a></p>
<p>Have questions, feedback, or security contributions? Reach out to our engineering team at <a href="mailto:security@orbixpanel.com"><code>security@orbixpanel.com</code></a>.\</p>
<p><em>Tags:</em> <code>#devops</code> <code>#security</code> <code>#opensource</code> <code>#selfhosted</code> <code>#golang</code></p>
]]></content:encoded></item><item><title><![CDATA[How We Built & Deployed MediQuick: Zero-Token Git Deployments on OrbixPanel]]></title><description><![CDATA[Connecting your self-hosted infrastructure to GitHub, GitLab, or Bitbucket shouldn't involve manually copying SSH keys, generating personal access tokens…]]></description><link>https://orbixpanel.hashnode.dev/how-we-built-deployed-mediquick-zero-token-git-deployments-on-orbixpanel</link><guid isPermaLink="true">https://orbixpanel.hashnode.dev/how-we-built-deployed-mediquick-zero-token-git-deployments-on-orbixpanel</guid><dc:creator><![CDATA[Maksudul Islam]]></dc:creator><pubDate>Mon, 09 Nov 2026 11:22:17 GMT</pubDate><enclosure url="https://cdn.hashnode.com/uploads/covers/6af1a897a83903c56a041dec/37c08e37-4750-48ef-b27f-e0feba1c6e25.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<h1>How We Built &amp; Deployed MediQuick: Zero-Token Git Deployments on OrbixPanel</h1>
<p>Connecting your self-hosted infrastructure to GitHub, GitLab, or Bitbucket shouldn't involve manually copying SSH keys, generating personal access tokens, or pasting repository URLs back and forth.</p>
<p>When building <strong><a href="https://mediquick.orbixpanel.com/">MediQuick</a></strong>—a fast medical information lookup engine that aggregates and formats clinical data from <strong>openFDA</strong>, <strong>DailyMed</strong>, and <strong>RxNorm</strong>—we wanted a deployment workflow that felt as frictionless as modern PaaS tools, but ran entirely on our own self-hosted servers.</p>
<p>In this post, we'll look at how <strong>OrbixPanel’s 1-Click OAuth Git Integration</strong> works under the hood and how we deployed MediQuick without pasting a single token or URL.</p>
<hr />
<h2>🏥 What is MediQuick?</h2>
<p><a href="https://mediquick.orbixpanel.com/">MediQuick</a> is a web application designed to query medical and pharmaceutical data across official public APIs:</p>
<ul>
<li><strong>openFDA:</strong> Real-time drug safety, adverse event reports, and recall data.</li>
<li><strong>DailyMed:</strong> Official FDA package insert labels and clinical medication guides.</li>
<li><strong>RxNorm:</strong> Normalized names for clinical drugs and link identifiers.</li>
</ul>
<p>When deploying a multi-API health tech application, you need quick iteration: push code to GitHub \(\rightarrow\) automatically build, deploy, and assign Let's Encrypt SSL.</p>
<hr />
<h2>🔒 The Challenge: Private Token Sprawl</h2>
<p>Normally, setting up self-hosted Git deployments forces you to choose between two annoying options:</p>
<ol>
<li><strong>Pasting Raw Git URLs &amp; Access Tokens:</strong> Exposing personal tokens in text boxes across various tools.</li>
<li><strong>Setting up Webhooks &amp; SSH Keys manually per repository:</strong> Time-consuming setup for every new app you build.</li>
</ol>
<hr />
<h2>⚡ The Solution: One-Time OAuth Registration</h2>
<p>OrbixPanel solves this by using <strong>1-Time OAuth Provider Integration</strong>. </p>
<h3>How it works:</h3>
<ol>
<li><strong>5-Minute One-Time Setup:</strong> You register an OAuth App inside your GitHub, GitLab, or Bitbucket account (setting your server's callback URL).</li>
<li><strong>Encrypted Credentials:</strong> Your OAuth Client ID and Secret stay encrypted locally on your OrbixPanel server.</li>
<li><strong>1-Click Deployment:</strong> Once connected, your panel automatically populates all your private and public repositories in a single list.</li>
</ol>
<p>Zero manual token management, zero public URL pasting. Just click <strong>"Deploy"</strong> next to your branch.</p>
<p><img src="REPLACE_WITH_IMAGE_1_URL" alt="GitHub OAuth Application Setup" /></p>
<figcaption>Registering a single OAuth App for OrbixPanel</figcaption>

<hr />
<h2>🚀 Step-by-Step: Deploying MediQuick via OAuth</h2>
<h3>1. Register the OAuth Provider (Once per Server)</h3>
<p>In your GitHub developer settings, create a new OAuth Application:</p>
<ul>
<li><strong>Application Name:</strong> <code>OrbixPanel</code></li>
<li><strong>Homepage URL:</strong> <code>https://&lt;your-server-domain&gt;</code></li>
<li><strong>Authorization Callback URL:</strong> <code>https://&lt;your-panel&gt;/api/git/callback/github</code></li>
</ul>
<p>Paste the generated Client ID and Client Secret into <strong>OrbixPanel \(\rightarrow\) Git Integrations</strong>.</p>
<h3>2. Select Repository &amp; Deploy</h3>
<p>Once authorized, OrbixPanel fetches your repository list securely. 
Find <code>orbixpanel/mediquick</code>, pick the branch (<code>main</code>), and hit <strong>Deploy</strong>.</p>
<p><img src="REPLACE_WITH_IMAGE_2_URL" alt="OrbixPanel Git Integrations Dashboard" /></p>
<figcaption>1-Click Git Repository Deployment Interface</figcaption>

<p>OrbixPanel handles the rest automatically:</p>
<ul>
<li>Clones the repository securely over OAuth.</li>
<li>Detects app environment &amp; builds dependencies.</li>
<li>Provisions Let's Encrypt SSL certificates.</li>
<li>Serves <code>https://mediquick.orbixpanel.com</code> behind a reverse proxy with zero downtime.</li>
</ul>
<hr />
<h2>🛡️ Security &amp; Privacy First</h2>
<p>Because OrbixPanel is self-hosted:</p>
<ul>
<li>Your OAuth tokens and access keys never hit 3rd-party servers or external clouds.</li>
<li>OAuth tokens are stored with AES encryption locally on your own server hardware.</li>
<li>You maintain total ownership over your deployment pipelines and API keys.</li>
</ul>
<hr />
<h2>💬 Try It Out</h2>
<p>Whether you are building healthcare apps like MediQuick, internal SaaS tools, or microservices, deployment should take seconds, not hours.</p>
<p>Check out live MediQuick at <strong><a href="https://mediquick.orbixpanel.com/">mediquick.orbixpanel.com</a></strong>, and test out 1-Click Git Deployments on your own VPS with <strong>OrbixPanel</strong> (Community Edition is FREE forever).</p>
<p>👉 <strong>Get Started:</strong> <a href="https://orbixpanel.com">orbixpanel.com</a></p>
]]></content:encoded></item></channel></rss>