<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: moktar</title>
    <description>The latest articles on DEV Community by moktar (@moktar_cffd734aa15706ed2c).</description>
    <link>https://dev.to/moktar_cffd734aa15706ed2c</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F1857171%2F41178afb-87b1-4250-9167-4b3db6e208c2.png</url>
      <title>DEV Community: moktar</title>
      <link>https://dev.to/moktar_cffd734aa15706ed2c</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/moktar_cffd734aa15706ed2c"/>
    <language>en</language>
    <item>
      <title>Keycloak y Authelia</title>
      <dc:creator>moktar</dc:creator>
      <pubDate>Thu, 05 Nov 2026 03:01:03 +0000</pubDate>
      <link>https://dev.to/moktar_cffd734aa15706ed2c/keycloak-y-authelia-3954</link>
      <guid>https://dev.to/moktar_cffd734aa15706ed2c/keycloak-y-authelia-3954</guid>
      <description>&lt;p&gt;&lt;strong&gt;Spanish Version&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Keycloak y Authelia resuelven la autenticación para problemas de diferente magnitud.&lt;/p&gt;

&lt;p&gt;Keycloak es una plataforma completa de gestión de identidades y accesos (IAM): federación de usuarios, flujos de inicio de sesión personalizados, políticas de autorización granulares y una consola de administración para controlarlo todo.&lt;br&gt;
Ponerlo en marcha significa operar un sistema IAM real, con la carga operativa que eso conlleva.&lt;/p&gt;

&lt;p&gt;Authelia se sitúa frente a los servicios existentes como una capa de autenticación frontal (forward-auth). Apunta tu proxy inverso (reverse proxy) hacia él y añadirá MFA y SSO a aplicaciones que nunca fueron diseñadas pensando en la autenticación.&lt;br&gt;
Sin consola de gestión de usuarios, sin federación de identidades. Responde a una sola pregunta: &lt;em&gt;¿se permite el paso a esta solicitud?&lt;/em&gt;, y lo hace muy bien.&lt;/p&gt;

&lt;p&gt;Un puñado de aplicaciones autoalojadas detrás de un proxy inverso, sin planes de federar identidades: elige Authelia, con sus 4 políticas por regla (bypass, one_factor, two_factor, deny) configuradas en una hora.&lt;/p&gt;

&lt;p&gt;Múltiples aplicaciones, proveedores de identidad externos y control de acceso basado en roles para una base de usuarios real: elige Keycloak, y planifica el tiempo que realmente necesita un despliegue IAM.&lt;/p&gt;

&lt;p&gt;Ambos son autoalojables, y ambos están listos para desplegar en tu propio servidor a través del catálogo de Railyard:&lt;br&gt;
&lt;a href="https://railyard.run/templates/keycloak/" rel="noopener noreferrer"&gt;https://railyard.run/templates/keycloak/&lt;/a&gt; / &lt;a href="https://railyard.run/templates/authelia/" rel="noopener noreferrer"&gt;https://railyard.run/templates/authelia/&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;¿Cuál de los dos protege tu infraestructura? ¿Y realmente encajaba con tu problema o fue simplemente el primer tutorial que encontraste?&lt;/p&gt;

&lt;h1&gt;
  
  
  Authelia #Keycloak #SelfHosted #AppSec #Railyard #DevOps
&lt;/h1&gt;

</description>
    </item>
    <item>
      <title>Escaping Heroku &amp; Render: Zero-Downtime `git push` Deploys on Your Own Server</title>
      <dc:creator>moktar</dc:creator>
      <pubDate>Wed, 04 Nov 2026 03:00:37 +0000</pubDate>
      <link>https://dev.to/moktar_cffd734aa15706ed2c/escaping-heroku-render-zero-downtime-git-push-deploys-on-your-own-server-46bf</link>
      <guid>https://dev.to/moktar_cffd734aa15706ed2c/escaping-heroku-render-zero-downtime-git-push-deploys-on-your-own-server-46bf</guid>
      <description>&lt;p&gt;Developers stay on Heroku, Render, and Railway because they love the &lt;code&gt;git push&lt;/code&gt; workflow, automatic database migrations, and zero-downtime health checks. They don't realize Railyard gives them that exact pipeline on their own cheap DigitalOcean or Hetzner VPS.&lt;/p&gt;




&lt;p&gt;Every developer eventually hits the PaaS wall. You start a project on Heroku, Render, or Railway because &lt;code&gt;git push&lt;/code&gt; deployments are magical. Fast forward six months: you add a couple of background workers, a Postgres database with &lt;code&gt;pgvector&lt;/code&gt;, and a Redis cache. Suddenly, you are paying $180/month for less than 4GB of total RAM.&lt;/p&gt;

&lt;p&gt;You want to move to a $10 DigitalOcean or Hetzner VPS, but you don't want to give up automatic builds, release hooks, and zero-downtime deploys.&lt;/p&gt;

&lt;p&gt;Here is how to replicate the exact Heroku &lt;code&gt;git push&lt;/code&gt; pipeline on your own cloud server using Railyard.&lt;/p&gt;

&lt;h3&gt;
  
  
  How Railyard's Build Pipeline Works
&lt;/h3&gt;

&lt;p&gt;Whether your repository uses a &lt;code&gt;Dockerfile&lt;/code&gt;, a &lt;code&gt;Procfile&lt;/code&gt;, &lt;code&gt;Nixpacks&lt;/code&gt;, or nothing at all (where Railyard defaults to &lt;code&gt;railpack&lt;/code&gt;), Railyard turns your code into an OCI image and runs it through a strict production release pipeline on your own server:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Build-Time Config Vars:&lt;/strong&gt; Environment variables are exported into the build environment (crucial for Next.js builds or Rails &lt;code&gt;assets:precompile&lt;/code&gt; steps that inspect &lt;code&gt;DATABASE_URL&lt;/code&gt;).&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Release Hooks:&lt;/strong&gt; Database migrations run in an isolated step &lt;em&gt;before&lt;/em&gt; the new container takes live traffic. If a migration fails, the deploy halts immediately.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Readiness Probes:&lt;/strong&gt; Traffic only swaps to the new container after your health check endpoint returns &lt;code&gt;HTTP 200&lt;/code&gt;.&lt;/li&gt;
&lt;/ol&gt;

&lt;h3&gt;
  
  
  Step 1: Connect Your Server and Provision Addons
&lt;/h3&gt;

&lt;ol&gt;
&lt;li&gt;Connect any Ubuntu server from DigitalOcean, Vultr, or Hetzner to &lt;a href="https://railyard.run" rel="noopener noreferrer"&gt;Railyard.run&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;Inside your Railyard project, provision your backing services in one click: &lt;strong&gt;Postgres (with &lt;code&gt;pgvector&lt;/code&gt; pre-installed)&lt;/strong&gt; and &lt;strong&gt;Redis&lt;/strong&gt;.&lt;/li&gt;
&lt;li&gt;Railyard spins these up on the same server (or a dedicated database server in your fleet) and automatically injects &lt;code&gt;DATABASE_URL&lt;/code&gt; and &lt;code&gt;REDIS_URL&lt;/code&gt; into your application environment.&lt;/li&gt;
&lt;/ol&gt;

&lt;h3&gt;
  
  
  Step 2: Configure Your Release Hook &amp;amp; Health Check
&lt;/h3&gt;

&lt;p&gt;If you are deploying a Ruby on Rails, Django, or Node.js app, you want migrations to run automatically on every deploy.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;If you use a &lt;code&gt;Procfile&lt;/code&gt;, define your web and release commands just like Heroku:
&lt;/li&gt;
&lt;/ul&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight yaml"&gt;&lt;code&gt;&lt;span class="na"&gt;release&lt;/span&gt;&lt;span class="pi"&gt;:&lt;/span&gt; &lt;span class="s"&gt;bundle exec rails db:migrate&lt;/span&gt;
&lt;span class="na"&gt;web&lt;/span&gt;&lt;span class="pi"&gt;:&lt;/span&gt; &lt;span class="s"&gt;bundle exec puma -C config/puma.rb&lt;/span&gt;
&lt;span class="na"&gt;worker&lt;/span&gt;&lt;span class="pi"&gt;:&lt;/span&gt; &lt;span class="s"&gt;bundle exec sidekiq&lt;/span&gt;

&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;ul&gt;
&lt;li&gt;Configure your health check path in Railyard (e.g., &lt;code&gt;GET /up&lt;/code&gt; or &lt;code&gt;GET /healthz&lt;/code&gt;).&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  Step 3: Push Your Code to Production
&lt;/h3&gt;

&lt;p&gt;You can connect your GitHub account for automatic deploys on commit, or push directly from your terminal using Git:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;&lt;span class="nv"&gt;$ &lt;/span&gt;git remote add railyard https://git.railyard.run/your-app.git
&lt;span class="nv"&gt;$ &lt;/span&gt;git push railyard main

&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Watch the terminal output as Railyard builds the app on your server, runs the migration hook, verifies the health check, and swaps traffic with zero dropped requests:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Enumerating objects: 12, done.
remote: Building storefront (Dockerfile)
remote: #7 RUN bundle install
remote: #9 RUN bin/rails assets:precompile
remote: Release: bin/rails db:migrate
remote: Health check passed (GET /up 200)
remote: Live, traffic moved to the new release.
To https://git.railyard.run/storefront.git
   a1b2c3d..e4f5a6b  main -&amp;gt; main

&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h3&gt;
  
  
  Step 4: Persistent Storage Without AWS S3 Headaches
&lt;/h3&gt;

&lt;p&gt;Unlike ephemeral PaaS dynos that wipe the filesystem on every restart, Railyard lets you attach &lt;strong&gt;named persistent volumes&lt;/strong&gt; directly to any path in your container (e.g., &lt;code&gt;/rails/storage&lt;/code&gt; or &lt;code&gt;/app/uploads&lt;/code&gt;) that survive across redeploys.&lt;/p&gt;




&lt;h3&gt;
  
  
  Bonus Growth Tip: Use Your "README Badge" Feature!
&lt;/h3&gt;

&lt;p&gt;On your &lt;code&gt;/templates/&lt;/code&gt; and &lt;code&gt;/deploy-methods/&lt;/code&gt; pages, Railyard already has a built-in feature for a &lt;strong&gt;"Deploy to Railyard" README badge&lt;/strong&gt; that opens a pre-filled deploy screen.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Whenever you write a tutorial about any of the &lt;strong&gt;337 apps&lt;/strong&gt; (like &lt;strong&gt;Typebot&lt;/strong&gt;, &lt;strong&gt;Windmill&lt;/strong&gt;, &lt;strong&gt;Typesense&lt;/strong&gt;, or &lt;strong&gt;SuperTokens&lt;/strong&gt;), put that markdown badge at the very top of your Dev.to and Medium articles so readers can click it and land directly in your signup flow!&lt;/li&gt;
&lt;/ul&gt;

</description>
      <category>webdev</category>
      <category>productivity</category>
      <category>programming</category>
      <category>tutorial</category>
    </item>
    <item>
      <title>How to Deploy n8n in "Queue Mode" on Hetzner for $5/mo (Beat Zapier's $500/mo Bill)</title>
      <dc:creator>moktar</dc:creator>
      <pubDate>Wed, 04 Nov 2026 02:59:25 +0000</pubDate>
      <link>https://dev.to/moktar_cffd734aa15706ed2c/how-to-deploy-n8n-in-queue-mode-on-hetzner-for-5mo-beat-zapiers-500mo-bill-9bb</link>
      <guid>https://dev.to/moktar_cffd734aa15706ed2c/how-to-deploy-n8n-in-queue-mode-on-hetzner-for-5mo-beat-zapiers-500mo-bill-9bb</guid>
      <description>&lt;p&gt;Standard self-hosted n8n instances crash under heavy webhook loads. Deploying n8n in "Queue Mode" (which requires Redis, Postgres, a main web process, and a separate background worker process) is notoriously painful to wire manually in Docker. Railyard has a verified 1-click template for this exact architecture.&lt;/p&gt;




&lt;p&gt;If you build heavy automations or AI workflows, Zapier and Make will bankrupt you as soon as your volume scales. The obvious move is self-hosting &lt;strong&gt;n8n&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;However, if you just run a basic &lt;code&gt;docker run n8n&lt;/code&gt; setup on a cheap server, your instance will choke the moment 50 webhooks hit it at the exact same time. To run n8n in production, you need &lt;strong&gt;Queue Mode&lt;/strong&gt;—an architecture where the main instance receives webhooks, pushes them to a &lt;strong&gt;Redis&lt;/strong&gt; queue, stores state in &lt;strong&gt;PostgreSQL&lt;/strong&gt;, and hands the heavy lifting off to dedicated &lt;strong&gt;background workers&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;Setting that up manually with Docker Compose, private networks, and reverse proxies takes hours. We are going to deploy a production-grade, multi-service n8n Queue Mode stack on a €4.50 (~$5) Hetzner server in 3 minutes using Railyard.&lt;/p&gt;

&lt;h3&gt;
  
  
  The Raw Cost Breakdown
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Zapier Team Plan (50,000 tasks/mo):&lt;/strong&gt; $399/month ($4,788/year)&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;n8n Cloud Pro (50,000 executions):&lt;/strong&gt; $120/month ($1,440/year)&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Self-Hosted n8n Queue Mode via Railyard:&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;Hetzner CX22 (2 vCPU, 4GB RAM): &lt;strong&gt;~$5.00/month&lt;/strong&gt;
&lt;/li&gt;
&lt;li&gt;Railyard Free Plan (Covers 1 server + 3 apps/stacks, zero compute markup): &lt;strong&gt;$0.00/month&lt;/strong&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Total: $5.00/month&lt;/strong&gt; (Unlimited workflows and executions)&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  Step 1: Provision a Bare Linux Box on Hetzner
&lt;/h3&gt;

&lt;ol&gt;
&lt;li&gt;Log into the Hetzner Cloud Console and create a new project.&lt;/li&gt;
&lt;li&gt;Add a server: Choose &lt;strong&gt;Ubuntu 24.04&lt;/strong&gt;, select the &lt;strong&gt;CX22&lt;/strong&gt; tier (4GB RAM gives plenty of breathing room for Redis, Postgres, and Node workers), and add your SSH key.&lt;/li&gt;
&lt;li&gt;Copy the public IPv4 address once the server comes online.&lt;/li&gt;
&lt;/ol&gt;

&lt;h3&gt;
  
  
  Step 2: Attach the Server to Railyard
&lt;/h3&gt;

&lt;p&gt;Railyard connects to your server via SSH and installs the container runtime, private networking mesh, and SSL proxy automatically.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Go to &lt;a href="https://railyard.run" rel="noopener noreferrer"&gt;Railyard.run&lt;/a&gt; and sign into your dashboard.&lt;/li&gt;
&lt;li&gt;Click &lt;strong&gt;Add Server&lt;/strong&gt; and enter your Hetzner IP address, user (&lt;code&gt;root&lt;/code&gt;), and SSH key.&lt;/li&gt;
&lt;li&gt;Railyard will initialize the node and set up the internal private network.&lt;/li&gt;
&lt;/ol&gt;

&lt;h3&gt;
  
  
  Step 3: Deploy the Verified "n8n (Queue Mode)" Template
&lt;/h3&gt;

&lt;p&gt;Instead of writing a 100-line &lt;code&gt;docker-compose.yml&lt;/code&gt; file to link Redis and Postgres, use Railyard's verified multi-service template.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Open the &lt;a href="https://railyard.run/templates/" rel="noopener noreferrer"&gt;Railyard Templates&lt;/a&gt; directory and filter by &lt;strong&gt;Automation&lt;/strong&gt;.&lt;/li&gt;
&lt;li&gt;Select &lt;strong&gt;n8n (queue mode)&lt;/strong&gt; (Verified 5-service stack).&lt;/li&gt;
&lt;li&gt;Click &lt;strong&gt;Deploy&lt;/strong&gt; and select your Hetzner server.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Behind the scenes, Railyard automatically provisions and wires together:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;PostgreSQL:&lt;/strong&gt; Replaces the default SQLite database so concurrent writes never lock up.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Redis:&lt;/strong&gt; Acts as the message broker between the web receiver and the workers.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;n8n Main:&lt;/strong&gt; Handles the UI and incoming webhook traffic.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;n8n Worker:&lt;/strong&gt; Pulls jobs from Redis and executes workflows in the background without slowing down the UI or dropping webhooks.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Private Networking:&lt;/strong&gt; All database and queue connection strings (&lt;code&gt;DB_POSTGRESDB_HOST&lt;/code&gt;, &lt;code&gt;QUEUE_BULL_REDIS_HOST&lt;/code&gt;, encryption keys) are injected into the build environment automatically over an isolated network.&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  Step 4: Lock Down Your Webhook URL with Automatic HTTPS
&lt;/h3&gt;

&lt;p&gt;OAuth callbacks (for Slack, Google, Stripe) require valid SSL certificates to function.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Point an &lt;code&gt;A&lt;/code&gt; record (e.g., &lt;code&gt;automate.yourdomain.com&lt;/code&gt;) to your Hetzner IP.&lt;/li&gt;
&lt;li&gt;Add the domain to your n8n app inside Railyard.&lt;/li&gt;
&lt;li&gt;Railyard provisions the Let's Encrypt certificate and configures the &lt;code&gt;WEBHOOK_URL&lt;/code&gt; environment variable so your production webhooks route properly on the first try.&lt;/li&gt;
&lt;/ol&gt;

</description>
      <category>productivity</category>
      <category>programming</category>
      <category>webdev</category>
      <category>tutorial</category>
    </item>
    <item>
      <title>Northflank Is Breached: The Shared-PaaS Model Has Officially Collapsed</title>
      <dc:creator>moktar</dc:creator>
      <pubDate>Sat, 31 Oct 2026 00:33:20 +0000</pubDate>
      <link>https://dev.to/moktar_cffd734aa15706ed2c/northflank-is-breached-the-shared-paas-model-has-officially-collapsed-1ace</link>
      <guid>https://dev.to/moktar_cffd734aa15706ed2c/northflank-is-breached-the-shared-paas-model-has-officially-collapsed-1ace</guid>
      <description>&lt;p&gt;With six major, lightning-fast breaches hitting multi-tenant cloud platforms PingCAP/TiDB, Fireworks AI, Zeabur, OpenCode Console, Railway, and now Northflank—the signal is unmistakable: the shared-tenant PaaS model is experiencing a systemic isolation failure.&lt;/p&gt;

&lt;p&gt;When multi-tenant Platform-as-a-Service (PaaS) providers run shared control planes and shared infrastructure pools across thousands of customers, a single tenant escape or platform-level zero-day compromises the entire trust boundary. Modern AI-accelerated automated exploits are targeting these shared chokepoints and firing for effect.&lt;/p&gt;

&lt;p&gt;The Alternative: Bring Your Own Server (BYOS)&lt;br&gt;
This escalating security emergency proves that outsourcing runtime hosting to shared multi-tenant clouds is a fundamental structural risk for production workloads. Modern engineering teams need the developer experience of a top-tier PaaS without inheriting the vulnerability radius of thousands of strangers on the same host.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://railyard.run" rel="noopener noreferrer"&gt;https://railyard.run&lt;/a&gt; solves this by shifting the deployment architecture to Bring Your Own Server (BYOS):&lt;/p&gt;

&lt;p&gt;Zero Co-Tenancy Isolation: Run workloads on your own dedicated compute (AWS, Hetzner, Bare Metal, or Private Cloud). Your compute, memory, and kernel boundaries are exclusively yours.&lt;/p&gt;

&lt;p&gt;Isolated Control Planes &amp;amp; Secrets: Key management, environment variables, and runtime execution never touch a shared multi-tenant memory pool.&lt;/p&gt;

&lt;p&gt;Minimized Blast Radius: A breach of any external workload or platform never propagates to your infrastructure—your cloud account remains strictly compartmentalized.&lt;/p&gt;

&lt;p&gt;War-Footing Hardening Protocol&lt;br&gt;
To survive automated, rapid-sequence attack cycles, security teams must move beyond hope-based security and implement zero-trust runtime controls:&lt;/p&gt;

&lt;p&gt;Deploy Single-Tenant Architecture (BYOS): Decouple orchestrators from shared public PaaS clouds. Host managed deployments directly inside customer-owned VPCs.&lt;/p&gt;

&lt;p&gt;Ephemeral Identity &amp;amp; Tripwire Secrets: Eliminate persistent static credentials. Enforce dynamic OIDC tokens, automated rotation schedules, and canary secrets that instantly signal unauthenticated access.&lt;/p&gt;

&lt;p&gt;Automated Kill-Switches &amp;amp; Rate Limits: Implement hard billing circuit breakers, automated runtime execution caps, and aggressive time-bound API tokens to halt automated exploitation in real time.&lt;/p&gt;

&lt;p&gt;Active Signal Monitoring &amp;amp; DFIR Preparedness: Stream immutable audit logs off-instance, enforce strict egress controls, and keep DFIR procedures pre-staged for immediate execution.&lt;/p&gt;

&lt;p&gt;The era of trusting multi-tenant PaaS vendors with shared runtime boundaries is over. Railyard.run delivers the seamless, frictionless workflow of modern cloud platforms while keeping your compute, data, and security perimeter entirely under your control.&lt;/p&gt;

&lt;p&gt;🔗 Take back control of your infrastructure: &lt;a href="https://railyard.run" rel="noopener noreferrer"&gt;https://railyard.run&lt;/a&gt;&lt;/p&gt;

&lt;h1&gt;
  
  
  DevOps#CloudSecurity#Infosec#BYOS#AppSec#PlatformEngineering#DevOps#CyberSecurity#CloudNative
&lt;/h1&gt;

</description>
      <category>devops</category>
      <category>cloud</category>
    </item>
    <item>
      <title>Your database on your own server, backed up on a schedule and restorable to a point in time.

https://railyard.run/features/?utm_source=devto&amp;utm_medium=social&amp;utm_campaign=autopilot&amp;utm_content=post-42</title>
      <dc:creator>moktar</dc:creator>
      <pubDate>Tue, 27 Oct 2026 13:36:17 +0000</pubDate>
      <link>https://dev.to/moktar_cffd734aa15706ed2c/your-database-on-your-own-server-backed-up-on-a-schedule-and-restorable-to-a-point-in-time-pd1</link>
      <guid>https://dev.to/moktar_cffd734aa15706ed2c/your-database-on-your-own-server-backed-up-on-a-schedule-and-restorable-to-a-point-in-time-pd1</guid>
      <description>&lt;div class="crayons-card c-embed text-styles text-styles--secondary"&gt;
    &lt;div class="c-embed__content"&gt;
        &lt;div class="c-embed__cover"&gt;
          &lt;a href="https://railyard.run/features/?utm_source=devto&amp;amp;amp%3Butm_medium=social&amp;amp;amp%3Butm_campaign=autopilot&amp;amp;amp%3Butm_content=post-42" class="c-link align-middle" rel="noopener noreferrer"&gt;
            &lt;img alt="" src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Frailyard.run%2Fog.png" height="420" class="m-0" width="800"&gt;
          &lt;/a&gt;
        &lt;/div&gt;
      &lt;div class="c-embed__body"&gt;
        &lt;h2 class="fs-xl lh-tight"&gt;
          &lt;a href="https://railyard.run/features/?utm_source=devto&amp;amp;amp%3Butm_medium=social&amp;amp;amp%3Butm_campaign=autopilot&amp;amp;amp%3Butm_content=post-42" rel="noopener noreferrer" class="c-link"&gt;
            Features · Railyard
          &lt;/a&gt;
        &lt;/h2&gt;
          &lt;p class="truncate-at-3"&gt;
            Canary releases, rollback with variables, managed databases with standbys and point-in-time restore, log drains, edge rules, autoscaling and SSO. On servers you own.
          &lt;/p&gt;
        &lt;div class="color-secondary fs-s flex items-center"&gt;
            &lt;img alt="favicon" class="c-embed__favicon m-0 mr-2 radius-0" src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Frailyard.run%2Ffavicon.svg" width="32" height="32"&gt;
          railyard.run
        &lt;/div&gt;
      &lt;/div&gt;
    &lt;/div&gt;
&lt;/div&gt;


</description>
    </item>
    <item>
      <title>You can try Railyard on a server you already have. Free plan: 1 server, a database server, 3 apps, no card.

https://railyard.run/?utm_source=devto&amp;utm_medium=social&amp;utm_campaign=autopilot&amp;utm_content=post-43</title>
      <dc:creator>moktar</dc:creator>
      <pubDate>Mon, 26 Oct 2026 21:35:56 +0000</pubDate>
      <link>https://dev.to/moktar_cffd734aa15706ed2c/you-can-try-railyard-on-a-server-you-already-have-free-plan-1-server-a-database-server-3-apps-cio</link>
      <guid>https://dev.to/moktar_cffd734aa15706ed2c/you-can-try-railyard-on-a-server-you-already-have-free-plan-1-server-a-database-server-3-apps-cio</guid>
      <description>&lt;div class="crayons-card c-embed text-styles text-styles--secondary"&gt;
    &lt;div class="c-embed__content"&gt;
        &lt;div class="c-embed__cover"&gt;
          &lt;a href="https://railyard.run/?utm_source=devto&amp;amp;amp%3Butm_medium=social&amp;amp;amp%3Butm_campaign=autopilot&amp;amp;amp%3Butm_content=post-43" class="c-link align-middle" rel="noopener noreferrer"&gt;
            &lt;img alt="" src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Frailyard.run%2Fog.png" height="420" class="m-0" width="800"&gt;
          &lt;/a&gt;
        &lt;/div&gt;
      &lt;div class="c-embed__body"&gt;
        &lt;h2 class="fs-xl lh-tight"&gt;
          &lt;a href="https://railyard.run/?utm_source=devto&amp;amp;amp%3Butm_medium=social&amp;amp;amp%3Butm_campaign=autopilot&amp;amp;amp%3Butm_content=post-43" rel="noopener noreferrer" class="c-link"&gt;
            Railyard: deploy full-stack apps to servers you own
          &lt;/a&gt;
        &lt;/h2&gt;
          &lt;p class="truncate-at-3"&gt;
            Deploy your frontend, backend, Postgres, Redis and workers to servers in your own cloud account. Flat price per team, no markup on compute.
          &lt;/p&gt;
        &lt;div class="color-secondary fs-s flex items-center"&gt;
            &lt;img alt="favicon" class="c-embed__favicon m-0 mr-2 radius-0" src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Frailyard.run%2Ffavicon.svg" width="32" height="32"&gt;
          railyard.run
        &lt;/div&gt;
      &lt;/div&gt;
    &lt;/div&gt;
&lt;/div&gt;


</description>
    </item>
    <item>
      <title>Railway and Heroku both got breached through shared infrastructure. Here's the actual pattern, not a sales pitch.</title>
      <dc:creator>moktar</dc:creator>
      <pubDate>Mon, 26 Oct 2026 14:31:13 +0000</pubDate>
      <link>https://dev.to/moktar_cffd734aa15706ed2c/railway-and-heroku-both-got-breached-through-shared-infrastructure-heres-the-actual-pattern-not-45ag</link>
      <guid>https://dev.to/moktar_cffd734aa15706ed2c/railway-and-heroku-both-got-breached-through-shared-infrastructure-heres-the-actual-pattern-not-45ag</guid>
      <description>&lt;p&gt;Two platforms that run a lot of other people’s applications have published real, confirmed security incidents in the last few years: Railway in October 2026, and Heroku in April 2022. Both are documented by the companies themselves, not rumor. And both trace back to the same underlying shape of risk: a vulnerability in infrastructure the platform operates on behalf of many customers at once, which turned into access to data belonging to customers who had nothing to do with the original flaw.&lt;/p&gt;

&lt;p&gt;This post isn’t “every platform has been breached” — that would be false, and we’re not going to claim it. It’s two real, well-documented incidents, what they actually have in common, and what a bring-your-own-server model changes about that specific pattern. We already wrote a full breakdown of the Railway incident on its own: Railway’s environment-variable breach. This post looks at the pattern across both.&lt;/p&gt;

&lt;p&gt;What actually happened, in both cases#&lt;br&gt;
Railway, October 2026. Railway’s own preliminary report describes an attacker who escalated privileges inside Railway’s build infrastructure, reached its CI environment, and from there accessed systems storing customer environment variables — decrypting a subset of them. By Railway’s own count, up to 1.85% of all workspaces, roughly 100,000, had some environment variables potentially exposed. The full timeline and Railway’s own words are in our dedicated breach post.&lt;/p&gt;

&lt;p&gt;Heroku, April 2022. A threat actor obtained a Heroku machine account’s credentials, which had been left in an archived private GitHub repository containing Heroku source code. That access reached a Heroku database storing customer GitHub integration OAuth tokens, and from there into an internal customer database, where hashed and salted customer passwords were exfiltrated. Heroku disclosed this on April 15, 2022, revoked the GitHub integration’s tokens, forced a password reset for affected users, and the GitHub integration itself stayed offline until May 25, 2022. GitHub’s own security team separately confirmed the stolen OAuth tokens were used to access private repositories across dozens of organizations, including npm’s.&lt;/p&gt;

&lt;p&gt;The pattern underneath both#&lt;br&gt;
Neither of these was a customer doing something wrong, and neither was a brute-force attack on an individual account. In both cases, the entry point was a piece of infrastructure the platform operates centrally — Railway’s build/CI pipeline, Heroku’s internal source control and machine-account credentials — and the exit point was data belonging to a large number of unrelated customers, reached through that one shared system.&lt;/p&gt;

&lt;p&gt;That’s the actual mechanism worth naming: on a multi-tenant platform, the build system, the control plane, and the compute that runs customer code all typically sit inside the same operator’s internal perimeter. A credential leak or privilege-escalation bug in any one of those systems is potentially a path into everyone’s data, because “everyone” shares the infrastructure that bug lives in.&lt;/p&gt;

&lt;p&gt;What a BYO-server model actually changes — and what it doesn’t#&lt;br&gt;
We wrote this carefully in the Railway post and it applies here too: Railyard’s own control plane stores customer environment variables centrally, encrypted at rest, the same general way any platform holding customer secrets does — Railway and Heroku included. A compromise of Railyard’s control-plane database and its encryption key is the same general class of risk any central secrets store carries, regardless of where the compute lives. Owning your own server doesn’t make that database disappear.&lt;/p&gt;

&lt;p&gt;What changes is what the decrypted, live copy of a secret touches once it leaves that store. On Railyard, variables are decrypted once, at deploy time, and delivered to a server in that specific customer’s own cloud account — not to a shared compute fleet the platform itself operates. There’s no single build pipeline or CI environment whose compromise hands an attacker a foothold in other customers’ running applications, because there isn’t a shared fleet of running applications to pivot through. Every customer’s live environment is a different machine in a different account.&lt;/p&gt;

&lt;p&gt;That’s a narrow, specific claim: it closes one path — a bug in shared platform infrastructure becoming a route into many unrelated customers’ live secrets at once — not every path. It is not a claim that Railyard, or anyone, is immune to a breach. A company that tells you it can’t be breached is a company you should be more skeptical of, not less.&lt;/p&gt;

&lt;p&gt;What to actually do about it, on any platform#&lt;br&gt;
Rotate secrets on a schedule, not just after a disclosure. A static, long-lived API key sitting in any platform’s dashboard is a standing liability independent of any one incident.&lt;br&gt;
Scope credentials tightly. The smaller the blast radius of a single leaked key, the less a breach of any kind costs you.&lt;br&gt;
Ask what has to be compromised to reach a decrypted secret in active use — not just whether data is “encrypted at rest.” Encryption at rest is table stakes everywhere; the real question is how many shared systems sit between a bug somewhere else on the platform and your actual running secrets.&lt;br&gt;
Read the incident reports companies actually publish. Railway’s and Heroku’s disclosures here are both genuinely informative when you read what they confirmed versus what got amplified secondhand — see our Railway breach breakdown for an example of separating the two.&lt;br&gt;
See the full comparisons: Railyard vs. Railway and Migrating from Heroku.&lt;/p&gt;

&lt;p&gt;FAQ#&lt;br&gt;
Has every PaaS been breached? No, and we’re not claiming that. This post covers two specific, confirmed, well-documented incidents — Railway (2026) and Heroku (2022) — not every platform in the market.&lt;/p&gt;

&lt;p&gt;Does running your own server make a breach impossible? No. A platform’s control plane still has to store your secrets somewhere before deploying them, and that store is a target on any architecture, Railyard included. What changes is whether a bug in the platform’s shared build/compute infrastructure can become a path into other customers’ live, running secrets — on a BYO-server model, there’s no shared compute fleet for that bug to pivot through.&lt;/p&gt;

&lt;p&gt;What’s the actual common thread between Railway’s and Heroku’s incidents? In both cases, the initial access point was infrastructure the platform operates on behalf of many customers at once (Railway’s build/CI pipeline; Heroku’s internal source control and machine-account credentials), and the impact reached customers who had nothing to do with the original vulnerability.&lt;/p&gt;

&lt;p&gt;Sources#&lt;br&gt;
Security Disclosure: Wednesday October 21st — Railway’s own blog&lt;br&gt;
Preliminary Report: Oct 21st Security Incident — Railway’s own blog&lt;br&gt;
April 2022 Incident Review — Heroku’s own blog&lt;br&gt;
Incident 2413 — Heroku’s own status page&lt;br&gt;
Security alert: Attack campaign involving stolen OAuth user tokens — GitHub’s own blog&lt;br&gt;
Heroku Forces User Password Resets Following GitHub OAuth Token Theft — secondary coverage&lt;br&gt;
For more : &lt;a href="https://railyard.run/blog/paas-breaches-shared-infrastructure-risk/" rel="noopener noreferrer"&gt;https://railyard.run/blog/paas-breaches-shared-infrastructure-risk/&lt;/a&gt;&lt;/p&gt;

</description>
    </item>
    <item>
      <title>Heroku is in sustaining engineering mode now, and that's a different kind of risk than a price increase</title>
      <dc:creator>moktar</dc:creator>
      <pubDate>Sat, 24 Oct 2026 04:33:39 +0000</pubDate>
      <link>https://dev.to/moktar_cffd734aa15706ed2c/heroku-is-in-sustaining-engineering-mode-now-and-thats-a-different-kind-of-risk-than-a-price-4gi1</link>
      <guid>https://dev.to/moktar_cffd734aa15706ed2c/heroku-is-in-sustaining-engineering-mode-now-and-thats-a-different-kind-of-risk-than-a-price-4gi1</guid>
      <description>&lt;p&gt;On February 6, 2026, Heroku’s chief product officer Nitin T Bhat published a short post titled “An Update on Heroku,” announcing that the platform was moving to what Salesforce calls a sustaining engineering model. The post is specific about what that means in practice: Enterprise Account contracts will no longer be offered to new customers, and the engineering focus going forward is “stability, security, reliability, and support,” with an explicit statement that this comes “rather than introducing new features.” Existing customers, the post says, see no immediate change: pricing, billing and day-to-day service stay the same, and existing Enterprise contracts continue to be honored and can renew. Salesforce’s own framing for the shift is that it’s redirecting product and engineering investment toward “areas where we can deliver the greatest long-term customer value,” specifically enterprise AI products, which is the actual business reason behind the change, stated plainly rather than inferred.&lt;/p&gt;

&lt;p&gt;This is a different kind of story than the pricing changes other platforms have made this year, and it deserves to be treated differently. A price going up or a bandwidth allowance getting cut is a cost question: run the numbers, decide if the new number still works. Software that stops moving forward is a different, slower-moving kind of risk, and it’s worth being precise about what it actually changes day to day, rather than reaching for either “nothing to worry about” or “Heroku is dead,” neither of which is accurate.&lt;/p&gt;

&lt;p&gt;What does “sustaining engineering” actually mean for Heroku users?&lt;br&gt;
The term itself isn’t exotic. It’s a recognized mode in long-lived commercial software: a product that’s past its growth phase gets a smaller, dedicated team whose job is keeping it running correctly, patched and secure, without the team that would normally be building what’s next. Heroku’s own post is careful to say this isn’t a shutdown notice. Apps already running stay running. Pipelines, teams, and the existing add-on ecosystem are explicitly called out as unaffected. Billing doesn’t change for customers paying by credit card through the dashboard. None of that is spin; it matches what sustaining engineering means everywhere else it’s used, and Heroku’s wording avoids overstating or understating it.&lt;/p&gt;

&lt;p&gt;What the post does confirm, directly, is the part that matters for anyone planning around Heroku for the next few years: no new features. Not “fewer” features, not “a slower cadence,” the stated posture is that new capability development is not what the team is doing anymore. Combined with no new Enterprise contracts for new customers, the practical read is that Heroku the product, as of February 2026, is not something a team should expect to keep up with developments in the broader platform space on. Whatever the buildpack ecosystem looks like in two years, whatever regions get added to competing platforms, whatever managed-database feature becomes standard elsewhere, Heroku’s answer to all of it is very likely “that’s not something we’re building,” because the team whose job that would have been isn’t doing that job anymore.&lt;/p&gt;

&lt;p&gt;What that costs in practice, for a team still on it today&lt;br&gt;
For a team with a stable app, modest growth, and no plans to add new kinds of workloads, this genuinely might not matter for a long while. The post is honest that existing functionality keeps working, and “stability, security, reliability and support” is a real commitment, not an empty one, assuming Salesforce holds to it. Security patches for the existing buildpack stack, bug fixes for existing features, these are explicitly still in scope.&lt;/p&gt;

&lt;p&gt;The exposure shows up in a few specific, foreseeable places. New framework or language runtime support is the first: a team that adopts a new version of a framework, or a language runtime Heroku hasn’t already built support for, has no reason to expect Heroku to add it, because that’s new feature work by definition. New regions are the second: infrastructure expansion is product development, and a company in sustaining mode has no stated reason to build new regions, which matters for any team whose latency requirements or compliance needs change over the life of the product. The third, and the one that compounds quietly, is responsiveness to bugs that aren’t security-critical: “stability and reliability” covers keeping existing behavior correct, but a non-critical bug that’s inconvenient rather than dangerous is exactly the kind of issue a smaller, maintenance-focused team reasonably deprioritizes, because that’s what a shrunk roadmap is for. None of these are catastrophic on their own. Together, over two or three years, they describe a platform that quietly falls further behind the part of the category that’s still actively built, while continuing to run correctly for exactly the workload it already supported on the day of the announcement.&lt;/p&gt;

&lt;p&gt;Why this is a structural risk specific to renting the whole stack&lt;br&gt;
The deeper point isn’t about Heroku specifically, it’s about what it means to depend entirely on one company’s product roadmap for your own infrastructure. On a fully managed platform, a customer has no path to keep the parts of the service they value moving forward if the vendor’s own priorities change. There’s no server to patch yourself, no infrastructure layer underneath the product that the customer still controls, the entire thing is the vendor’s roadmap, and when that roadmap gets reprioritized, every customer’s future capability gets reprioritized along with it, with no way to opt out short of leaving the platform entirely.&lt;/p&gt;

&lt;p&gt;That’s the specific risk sustaining engineering represents, and it’s worth being fair about why Salesforce made the call: a 2026 enterprise software company redirecting investment toward enterprise AI is a rational business decision given the market, and Heroku, nearly two decades old, is a mature product with a well-known shape rather than a growth bet. Nothing about the decision is reckless or dishonest, the announcement itself is unusually direct about what’s changing and why. The risk isn’t that Salesforce did something wrong. It’s that any customer fully inside one company’s managed stack has no lever to pull when that company’s internal priorities shift, because the infrastructure was never theirs to begin with.&lt;/p&gt;

&lt;p&gt;What a BYO-server model changes about this specific risk&lt;br&gt;
A platform that runs on servers the customer owns can’t fully eliminate this risk, the control-plane software itself is still built by a company with its own roadmap and its own priorities that could shift. But it changes what’s actually at stake if that happens. The server itself, a plain Linux box at DigitalOcean, Hetzner or Vultr, running an ordinary Docker container behind a standard reverse proxy, doesn’t go stale because the control plane’s roadmap changes. If Railyard stopped shipping new features tomorrow, the apps already deployed keep running on infrastructure the customer already owns and controls directly over SSH, with no dependency on Railyard’s continued development to keep serving traffic. The worst case for a customer in that scenario is losing access to a dashboard and some automation convenience, not losing the infrastructure the app actually runs on, because that infrastructure was never the vendor’s to begin with.&lt;/p&gt;

&lt;p&gt;That’s the structural answer to “what if the company behind my platform deprioritizes it,” and it’s a meaningfully different answer than anything available to a customer on a fully managed platform. It doesn’t require Railyard, or any BYO-server platform, to promise it will never happen here; it requires the architecture to make the consequence survivable if it does, which is a guarantee a rented stack can’t offer no matter how well-run the vendor is.&lt;/p&gt;

&lt;p&gt;The honest takeaway&lt;br&gt;
Heroku’s February 2026 announcement isn’t a crisis for anyone running on it today, and it isn’t dishonest or poorly communicated, if anything it’s a more direct statement than most companies give when deprioritizing a mature product. The actual lesson is about the category of risk itself: a team that depends entirely on a managed platform is also, by construction, depending entirely on that one company’s internal roadmap decisions staying aligned with the team’s own needs indefinitely, with no fallback if they stop being aligned. That’s a real structural property of renting the whole stack, independent of how good or bad any particular vendor’s intentions are, and it’s worth weighing on its own terms, separately from whatever the current pricing or feature set looks like on the day a team signs up.&lt;/p&gt;

&lt;p&gt;FAQ&lt;br&gt;
When did Heroku enter sustaining engineering mode? Heroku’s chief product officer, Nitin T Bhat, announced the shift on February 6, 2026, in a post titled “An Update on Heroku.”&lt;/p&gt;

&lt;p&gt;Is Heroku shutting down? No. Existing apps, pipelines, teams and add-ons keep working, and credit-card customers see no change to pricing or billing. Sustaining engineering means no new features and no new Enterprise contracts for new customers, not a shutdown.&lt;/p&gt;

&lt;p&gt;Will Heroku add new features or regions? The announcement is explicit that new feature development is not the team’s focus going forward, which also means new regions and new framework or runtime support shouldn’t be expected.&lt;/p&gt;

&lt;p&gt;Is this a bigger risk than a price increase? It’s a different kind of risk. A price increase is a cost question you can calculate once. A platform that stops moving forward is a risk that compounds slowly over years, as the rest of the category keeps shipping and a frozen platform doesn’t.&lt;/p&gt;

&lt;p&gt;Sources&lt;br&gt;
Heroku: “An Update on Heroku,” by Nitin T Bhat, Chief Product Officer, published February 6, 2026, Heroku and Salesforce’s own primary announcement&lt;br&gt;
DeployHQ: “Heroku Enters Sustaining Engineering Mode: What It Means and When to Consider Alternatives”, analysis of the practical implications&lt;br&gt;
DevClass: “Heroku future in doubt as Salesforce freezes features to focus on AI”, independent coverage of the February 2026 announcement&lt;br&gt;
Railyard’s own how it works page for details on running apps directly on infrastructure you control&lt;/p&gt;

&lt;p&gt;See how Railyard specifically compares for a team evaluating a move: Compare Railyard to Heroku, or see how Railyard runs on servers you own.&lt;/p&gt;

</description>
      <category>cloud</category>
      <category>news</category>
      <category>product</category>
    </item>
    <item>
      <title>Self-hosted Plausible analytics, in one command</title>
      <dc:creator>moktar</dc:creator>
      <pubDate>Thu, 22 Oct 2026 01:00:18 +0000</pubDate>
      <link>https://dev.to/moktar_cffd734aa15706ed2c/self-hosted-plausible-analytics-in-one-command-12j3</link>
      <guid>https://dev.to/moktar_cffd734aa15706ed2c/self-hosted-plausible-analytics-in-one-command-12j3</guid>
      <description>&lt;p&gt;For a while, railyard.run ran with zero analytics. Not out of principle — we just hadn’t gotten to it, which meant every “is anyone actually reading this” question was a guess. Fixing it became the first real test of whether “self-hosted, one click” actually holds up for something we’d use ourselves, not just something we built for other people’s apps.&lt;/p&gt;

&lt;p&gt;What we launched#&lt;br&gt;
Plausible Community Edition, as a Railyard stack template: three services — Plausible itself, Postgres for its own app data, and ClickHouse for the actual analytics events — provisioned together on one of our own servers.&lt;/p&gt;

&lt;p&gt;railyard launch plausible --server Copy&lt;br&gt;
That’s the whole provisioning step. No separate ClickHouse setup, no wiring connection strings by hand — the template declares all three services and how they talk to each other, and Railyard deploys the set as one unit.&lt;/p&gt;

&lt;p&gt;What came after the launch command#&lt;br&gt;
The rest was the normal first-run of any self-hosted app, not anything Railyard-specific:&lt;/p&gt;

&lt;p&gt;Open the app’s URL, sign up as the instance owner — Plausible’s own first-run flow, nothing to pre-seed.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Add a website, enter the domain being tracked.
Copy the tracking snippet it generates and drop it in the site’s .
No custom domain was even necessary — the app’s default *.apps.railyard.run URL was enough to run the dashboard and serve the tracking script. We only use that path because it’s genuinely simpler, not because anything was missing.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Where it actually broke, briefly#&lt;br&gt;
It didn’t — which is itself worth saying plainly, since the point of posting this at all is to be honest about what self-hosting something actually costs in practice. The template launched clean, the three services found each other over Railyard’s private networking without any manual env var wiring, and the tracking script started showing pageviews in Plausible’s Realtime view within seconds of being added to the site.&lt;/p&gt;

&lt;p&gt;The one thing worth knowing going in: a fresh launch creates a new app every time you run it, so launching twice means two full stacks running side by side, not an update to the first one. Easy mistake, easy fix — apps:rm  --confirm  in the CLI removes the extra one cleanly.&lt;/p&gt;

&lt;p&gt;Why self-hosted instead of Plausible Cloud#&lt;br&gt;
Plausible Cloud is a fine product and the simpler choice for most teams. We picked self-hosted specifically because it’s the same category of claim we make about everything else on Railyard: you should be able to run the tools you depend on, on infrastructure you control, without a second vendor relationship for every piece of your stack. Cookie-free, no consent banner, and the data never leaves a server we provisioned ourselves.&lt;/p&gt;

&lt;p&gt;If you’re weighing the same tradeoff for your own site, the Plausible template is one click away, and Logs, metrics and alerts covers the rest of what Railyard surfaces about traffic without a separate analytics stack at all.&lt;/p&gt;

&lt;p&gt;for more : &lt;a href="https://railyard.run/blog/self-hosted-analytics/" rel="noopener noreferrer"&gt;https://railyard.run/blog/self-hosted-analytics/&lt;/a&gt;&lt;/p&gt;

</description>
      <category>analytics</category>
      <category>automation</category>
      <category>database</category>
      <category>devops</category>
    </item>
  </channel>
</rss>
