{"id":480,"date":"2026-06-29T15:20:30","date_gmt":"2026-06-29T15:20:30","guid":{"rendered":"https:\/\/windows-vps.org\/blog\/?p=480"},"modified":"2026-06-29T15:20:30","modified_gmt":"2026-06-29T15:20:30","slug":"windows-vps-cicd-azure-devops-github-actions-build-agents","status":"publish","type":"post","link":"https:\/\/windows-vps.org\/blog\/windows-vps-cicd-azure-devops-github-actions-build-agents\/","title":{"rendered":"Windows VPS for CI\/CD: Setting Up Azure DevOps and GitHub Actions Build Agents"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">Continuous Integration and Continuous Deployment (CI\/CD) pipelines that target Windows environments \u2014 .NET applications, SQL Server databases, or desktop applications \u2014 require Windows-based build agents to compile, test, and package the code. Instead of using Microsoft-hosted agents (which incur per-minute costs and have limited customization), many teams deploy their own Windows VPS as a self-hosted build agent. This guide covers setting up Azure DevOps and GitHub Actions build agents on a Windows VPS, including security considerations, scalability, and cost optimization.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Why Use a Self-Hosted Windows VPS for CI\/CD?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Before diving into setup, consider the advantages of running your own build agent on a Windows VPS:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Cost savings at scale<\/strong> \u2014 Microsoft-hosted agents cost $0.04-$0.08 per minute for Windows. A team running 500 build minutes\/day would pay $600-$1,200\/month. A Windows VPS for the same workload costs $20-$50\/month with no per-minute fees.<\/li>\n<li><strong>Full software control<\/strong> \u2014 Install any SDK, toolchain, certificate, or dependency without waiting for Microsoft to update their agent images. Need .NET 10 preview or a specific Visual Studio version? Install it immediately.<\/li>\n<li><strong>Persistent storage<\/strong> \u2014 Cache NuGet packages, npm modules, and build artifacts between runs. This dramatically speeds up subsequent builds (often 50-70% faster).<\/li>\n<li><strong>Compliance and data sovereignty<\/strong> \u2014 Source code and build artifacts never leave your VPS. This is critical for regulated industries that cannot upload proprietary code to shared Microsoft-hosted infrastructure.<\/li>\n<li><strong>Custom hardware<\/strong> \u2014 Choose a VPS with the exact CPU, RAM, and storage your builds require. For large monorepos or complex builds, 8+ vCPU and 16+ GB RAM can cut build times by 75% compared to standard hosted agents.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Need a Windows VPS for your build infrastructure? <a href=\"https:\/\/windows-vps.org\/#providers\">Compare Windows VPS plans on our comparison table<\/a> to find a provider with the CPU and RAM your pipelines need.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Setting Up an Azure DevOps Self-Hosted Agent<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Prerequisites<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>A Windows VPS (Windows Server 2022 or 2025 recommended) with at least 4 GB RAM and 2 vCPU<\/li>\n<li>RDP or PowerShell Remoting access<\/li>\n<li>An Azure DevOps organization and project<\/li>\n<li>A Personal Access Token (PAT) with Agent Pools (read, manage) scope<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Step 1: Install Required Software<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">On your Windows VPS, install the development tools your pipelines need. At minimum, most .NET pipelines require:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code># Install .NET SDK (adjust version as needed)\nwinget install Microsoft.DotNet.SDK.10\n\n# Install Git\nwinget install Git.Git\n\n# Install NuGet CLI\nwinget install Microsoft.NuGet\n\n# For legacy .NET Framework builds, install Visual Studio Build Tools\n# Download from: https:\/\/visualstudio.microsoft.com\/downloads\/#build-tools-for-visual-studio-2022<\/code><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\">Step 2: Download and Configure the Agent<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Create a dedicated directory for the agent (avoid spaces in the path) and download the agent package:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code># Create agent directory\nmkdir C:gentsuild-agent-01\ncd C:gentsuild-agent-01\n\n# Download latest agent (check https:\/\/github.com\/Microsoft\/azure-pipelines-agent for latest version)\nInvoke-WebRequest -Uri \"https:\/\/vstsagentpackage.azureedge.net\/agent\/4.248.0\/vsts-agent-win-x64-4.248.0.zip\" -OutFile agent.zip\nExpand-Archive -Path agent.zip -DestinationPath .\n\n# Configure the agent\n.\\config.cmd --unattended --url https:\/\/dev.azure.com\/your-organization --auth pat --token YOUR_PAT --pool \"Default\" --agent \"win-vps-agent-01\" --runAsService --windowsLogonAccount \"NT AUTHORITY\\SYSTEM\"<\/code><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\">Step 3: Verify and Test<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">After configuration, the agent runs as a Windows service. Verify it appears online in Azure DevOps &gt; Project Settings &gt; Agent Pools &gt; Default &gt; Agents. Run a test pipeline to confirm builds execute correctly on your self-hosted agent.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Setting Up a GitHub Actions Self-Hosted Runner<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Prerequisites<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>A Windows VPS (Windows Server 2022 or 2025) with at least 4 GB RAM and 2 vCPU<\/li>\n<li>A GitHub account with admin access to the target repository or organization<\/li>\n<li>A GitHub Personal Access Token (classic, with repo scope) or a GitHub App installation token<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Step 1: Download and Configure the Runner<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">GitHub Actions runners use the same agent technology as Azure DevOps. On your Windows VPS:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code># Create runner directory\nmkdir C:ctions-runners\\my-runner\ncd C:ctions-runners\\my-runner\n\n# Download the latest runner (check https:\/\/github.com\/actions\/runner\/releases for latest)\nInvoke-WebRequest -Uri \"https:\/\/github.com\/actions\/runner\/releases\/download\/v2.322.0\/actions-runner-win-x64-2.322.0.zip\" -OutFile runner.zip\nExpand-Archive -Path runner.zip -DestinationPath .\n\n# Configure the runner (use the token from GitHub &gt; Settings &gt; Actions &gt; Runners)\n.\\config.cmd --url https:\/\/github.com\/your-organization\/your-repo --token YOUR_REGISTRATION_TOKEN --name \"win-vps-runner-01\" --labels \"windows,.net,sql\" --runasservice<\/code><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\">Step 2: Start the Runner Service<\/h3>\n\n\n\n<pre class=\"wp-block-code\"><code># Install and start the service\n.\\svc.cmd install\n.\\svc.cmd start\n\n# Verify status\n.\\svc.cmd status<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Once running, the runner appears as &#8220;Online&#8221; in GitHub &gt; Repository &gt; Settings &gt; Actions &gt; Runners. You can reference it in workflow files using the labels you configured:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>jobs:\n  build:\n    runs-on: [self-hosted, windows, .net, sql]\n    steps:\n      - uses: actions\/checkout@v4\n      - name: Build\n        run: dotnet build -c Release<\/code><\/pre>\n\n\n\n<h2 class=\"wp-block-heading\">Security Best Practices for Self-Hosted Agents<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Self-hosted build agents run arbitrary code from your pipelines. Follow these practices to keep them secure:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Dedicated VPS for builds only<\/strong> \u2014 Do not run web servers or other services on the same VPS. A compromised build pipeline could expose those services. Use a separate Windows VPS exclusively for CI\/CD.<\/li>\n<li><strong>Least-privilege service account<\/strong> \u2014 Run the agent as a dedicated local account (not Administrator) with minimal permissions. The agent service account needs only write access to the build workspace directory.<\/li>\n<li><strong>Ephemeral agents for untrusted code<\/strong> \u2014 If your pipelines run code from forked repositories or external contributors, use ephemeral (container-based or VM-based) agents that are destroyed after each job, not persistent VPS agents.<\/li>\n<li><strong>Network isolation<\/strong> \u2014 Place the build VPS on a separate virtual network or subnet with restricted outbound access. Build agents typically only need outbound HTTPS access to your VCS provider and NuGet\/npm registries.<\/li>\n<li><strong>Regular patching<\/strong> \u2014 Keep the Windows VPS fully patched. Build agents need the same security updates as any production server. Configure automatic Windows Update during off-hours.<\/li>\n<li><strong>Secret management<\/strong> \u2014 Use Azure DevOps Variable Groups or GitHub Actions Secrets instead of hardcoding credentials in pipeline YAML. The agent service account should not have access to secret files on disk.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">Scaling Self-Hosted Build Agents<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">As your team grows, you may need multiple build agents. Options for scaling include:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Multiple agents on one VPS<\/strong> \u2014 Install multiple agent instances in separate directories, each configured with a unique name. A VPS with 8 vCPU and 16 GB RAM can comfortably run 4-6 build agents simultaneously, as long as individual builds are not CPU-bound.<\/li>\n<li><strong>Multiple VPS instances<\/strong> \u2014 Provision separate Windows VPS instances for different teams or project groups. This isolates workloads and prevents a single heavy build from starving other teams.<\/li>\n<li><strong>Auto-scaling with Azure VM Scale Sets<\/strong> \u2014 Azure DevOps supports elastic agent pools that automatically provision and deprovision VMs based on pipeline demand. This is the most cost-effective approach for variable workloads.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">Cost Analysis: Self-Hosted vs. Microsoft-Hosted Agents<\/h2>\n\n\n\n<figure class=\"wp-block-table\"><table><thead><tr><th>Metric<\/th><th>Microsoft-Hosted (Standard)<\/th><th>Self-Hosted Windows VPS<\/th><\/tr><\/thead><tbody><tr><td>Per-minute cost<\/td><td>$0.04\/min (Windows)<\/td><td>$0 (flat monthly)<\/td><\/tr><tr><td>Monthly cost (500 min\/day)<\/td><td>$600<\/td><td>$20-$50<\/td><\/tr><tr><td>vCPU<\/td><td>2 (shared)<\/td><td>2-8 (dedicated)<\/td><\/tr><tr><td>RAM<\/td><td>7 GB<\/td><td>4-32 GB<\/td><\/tr><tr><td>Software customization<\/td><td>Limited to pre-installed images<\/td><td>Full control<\/td><\/tr><tr><td>Build cache persistence<\/td><td>No (fresh VM each run)<\/td><td>Yes (persistent disk)<\/td><\/tr><tr><td>Maintenance responsibility<\/td><td>Microsoft<\/td><td>You<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">For teams running more than 500 build minutes per month, self-hosted agents on a Windows VPS are typically 80-90% cheaper than Microsoft-hosted agents, with the added benefit of faster builds thanks to persistent caches and dedicated CPU resources.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Conclusion<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Setting up a self-hosted CI\/CD build agent on a Windows VPS is a straightforward process that yields significant cost savings and performance benefits for teams running Windows-targeted pipelines. Whether you use Azure DevOps or GitHub Actions, the configuration follows the same pattern: prepare your VPS with the required SDKs, download the agent software, configure authentication, and register it with your project. With persistent caches, dedicated hardware, and full software control, a self-hosted Windows VPS agent can cut build times by 50-75% while reducing CI\/CD costs by 80% or more compared to Microsoft-hosted alternatives. <a href=\"https:\/\/windows-vps.org\/#providers\">Compare Windows VPS plans on our comparison table<\/a> to find a provider with the dedicated CPU and RAM your build pipelines require.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Continuous Integration and Continuous Deployment (CI\/CD) pipelines that target Windows environments \u2014 .NET applications, SQL Server databases, or desktop applications \u2014 require Windows-based build agents to compile, test, and package the code. Instead of using Microsoft-hosted agents (which incur per-minute costs and have limited customization), many teams deploy their own Windows VPS as a self-hosted &#8230; <a title=\"Windows VPS for CI\/CD: Setting Up Azure DevOps and GitHub Actions Build Agents\" class=\"read-more\" href=\"https:\/\/windows-vps.org\/blog\/windows-vps-cicd-azure-devops-github-actions-build-agents\/\" aria-label=\"Read more about Windows VPS for CI\/CD: Setting Up Azure DevOps and GitHub Actions Build Agents\">Read more<\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"iawp_total_views":1,"footnotes":""},"categories":[5],"tags":[],"class_list":["post-480","post","type-post","status-publish","format-standard","hentry","category-tutorials-guides"],"yoast_head":"<!-- This site is optimized with the Yoast SEO Premium plugin v26.1 (Yoast SEO v26.1) - https:\/\/yoast.com\/wordpress\/plugins\/seo\/ -->\n<title>Windows VPS for CI\/CD: Setting Up Azure DevOps and GitHub Actions Build Agents - Windows VPS Blog<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/windows-vps.org\/blog\/windows-vps-cicd-azure-devops-github-actions-build-agents\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Windows VPS for CI\/CD: Setting Up Azure DevOps and GitHub Actions Build Agents\" \/>\n<meta property=\"og:description\" content=\"Windows VPS for CI\/CD: Setting Up Azure DevOps and GitHub Actions Build Agents\" \/>\n<meta property=\"og:url\" content=\"https:\/\/windows-vps.org\/blog\/windows-vps-cicd-azure-devops-github-actions-build-agents\/\" \/>\n<meta property=\"og:site_name\" content=\"Windows VPS Blog\" \/>\n<meta property=\"article:published_time\" content=\"2026-06-29T15:20:30+00:00\" \/>\n<meta name=\"author\" content=\"windows-vps\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"windows-vps\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"6 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/windows-vps.org\/blog\/windows-vps-cicd-azure-devops-github-actions-build-agents\/\",\"url\":\"https:\/\/windows-vps.org\/blog\/windows-vps-cicd-azure-devops-github-actions-build-agents\/\",\"name\":\"Windows VPS for CI\/CD: Setting Up Azure DevOps and GitHub Actions Build Agents - Windows VPS Blog\",\"isPartOf\":{\"@id\":\"https:\/\/windows-vps.org\/blog\/#website\"},\"datePublished\":\"2026-06-29T15:20:30+00:00\",\"author\":{\"@id\":\"https:\/\/windows-vps.org\/blog\/#\/schema\/person\/44caceed916d0db318aa08d5623a7a58\"},\"breadcrumb\":{\"@id\":\"https:\/\/windows-vps.org\/blog\/windows-vps-cicd-azure-devops-github-actions-build-agents\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/windows-vps.org\/blog\/windows-vps-cicd-azure-devops-github-actions-build-agents\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/windows-vps.org\/blog\/windows-vps-cicd-azure-devops-github-actions-build-agents\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/windows-vps.org\/blog\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Windows VPS for CI\/CD: Setting Up Azure DevOps and GitHub Actions Build Agents\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/windows-vps.org\/blog\/#website\",\"url\":\"https:\/\/windows-vps.org\/blog\/\",\"name\":\"Windows VPS Blog\",\"description\":\"\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/windows-vps.org\/blog\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Person\",\"@id\":\"https:\/\/windows-vps.org\/blog\/#\/schema\/person\/44caceed916d0db318aa08d5623a7a58\",\"name\":\"windows-vps\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/windows-vps.org\/blog\/#\/schema\/person\/image\/\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/3f2573db5afcd1a6ab9abcc5d48fc8e42584bc87ab9d98cc156e5b2097766dd9?s=96&d=mm&r=g\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/3f2573db5afcd1a6ab9abcc5d48fc8e42584bc87ab9d98cc156e5b2097766dd9?s=96&d=mm&r=g\",\"caption\":\"windows-vps\"},\"sameAs\":[\"https:\/\/windows-vps.org\/blog\"],\"url\":\"https:\/\/windows-vps.org\/blog\/author\/myxiechengxuan\/\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"Windows VPS for CI\/CD: Setting Up Azure DevOps and GitHub Actions Build Agents - Windows VPS Blog","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/windows-vps.org\/blog\/windows-vps-cicd-azure-devops-github-actions-build-agents\/","og_locale":"en_US","og_type":"article","og_title":"Windows VPS for CI\/CD: Setting Up Azure DevOps and GitHub Actions Build Agents","og_description":"Windows VPS for CI\/CD: Setting Up Azure DevOps and GitHub Actions Build Agents","og_url":"https:\/\/windows-vps.org\/blog\/windows-vps-cicd-azure-devops-github-actions-build-agents\/","og_site_name":"Windows VPS Blog","article_published_time":"2026-06-29T15:20:30+00:00","author":"windows-vps","twitter_card":"summary_large_image","twitter_misc":{"Written by":"windows-vps","Est. reading time":"6 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/windows-vps.org\/blog\/windows-vps-cicd-azure-devops-github-actions-build-agents\/","url":"https:\/\/windows-vps.org\/blog\/windows-vps-cicd-azure-devops-github-actions-build-agents\/","name":"Windows VPS for CI\/CD: Setting Up Azure DevOps and GitHub Actions Build Agents - Windows VPS Blog","isPartOf":{"@id":"https:\/\/windows-vps.org\/blog\/#website"},"datePublished":"2026-06-29T15:20:30+00:00","author":{"@id":"https:\/\/windows-vps.org\/blog\/#\/schema\/person\/44caceed916d0db318aa08d5623a7a58"},"breadcrumb":{"@id":"https:\/\/windows-vps.org\/blog\/windows-vps-cicd-azure-devops-github-actions-build-agents\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/windows-vps.org\/blog\/windows-vps-cicd-azure-devops-github-actions-build-agents\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/windows-vps.org\/blog\/windows-vps-cicd-azure-devops-github-actions-build-agents\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/windows-vps.org\/blog\/"},{"@type":"ListItem","position":2,"name":"Windows VPS for CI\/CD: Setting Up Azure DevOps and GitHub Actions Build Agents"}]},{"@type":"WebSite","@id":"https:\/\/windows-vps.org\/blog\/#website","url":"https:\/\/windows-vps.org\/blog\/","name":"Windows VPS Blog","description":"","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/windows-vps.org\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Person","@id":"https:\/\/windows-vps.org\/blog\/#\/schema\/person\/44caceed916d0db318aa08d5623a7a58","name":"windows-vps","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/windows-vps.org\/blog\/#\/schema\/person\/image\/","url":"https:\/\/secure.gravatar.com\/avatar\/3f2573db5afcd1a6ab9abcc5d48fc8e42584bc87ab9d98cc156e5b2097766dd9?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/3f2573db5afcd1a6ab9abcc5d48fc8e42584bc87ab9d98cc156e5b2097766dd9?s=96&d=mm&r=g","caption":"windows-vps"},"sameAs":["https:\/\/windows-vps.org\/blog"],"url":"https:\/\/windows-vps.org\/blog\/author\/myxiechengxuan\/"}]}},"_links":{"self":[{"href":"https:\/\/windows-vps.org\/blog\/wp-json\/wp\/v2\/posts\/480","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/windows-vps.org\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/windows-vps.org\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/windows-vps.org\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/windows-vps.org\/blog\/wp-json\/wp\/v2\/comments?post=480"}],"version-history":[{"count":1,"href":"https:\/\/windows-vps.org\/blog\/wp-json\/wp\/v2\/posts\/480\/revisions"}],"predecessor-version":[{"id":481,"href":"https:\/\/windows-vps.org\/blog\/wp-json\/wp\/v2\/posts\/480\/revisions\/481"}],"wp:attachment":[{"href":"https:\/\/windows-vps.org\/blog\/wp-json\/wp\/v2\/media?parent=480"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/windows-vps.org\/blog\/wp-json\/wp\/v2\/categories?post=480"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/windows-vps.org\/blog\/wp-json\/wp\/v2\/tags?post=480"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}