Migrating a dozen side projects from Azure to one VPS with an LLM agent

May 24, 2026 · 1:52 PM UTC ·6 min read · 0 reactions · 0 comments · 40 views

TL;DR · WeSearch summary

The author successfully migrated multiple side projects from Azure to a single VPS using an LLM coding agent. This transition simplified management and reduced costs while enhancing efficiency. The author highlights the ease of migration and the benefits of using LLM technology for repetitive tasks.

Key facts

▪The author moved over a dozen side projects from Azure to a single VPS.
▪The migration process was made easier with the help of an LLM coding agent, which automated many repetitive tasks.
▪The new setup includes various technologies like .NET APIs, Node/Express frontends, and Cloudflare for DNS and SSL management.

About this source

Hacker News (AI / LLM) files mainly under ai. We currently carry 3,362 of its stories.

All Hacker News (AI / LLM) coverage →

Original article

Victor A

Read full at Victor A →

Story provenance

Source · retrieval · rights · ranking — open for full record

inspect →

Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.

Record

Original publisher	Victor A
Canonical URL	https://victorantos.com/posts/from-azure-to-one-vps-llm-migration/
Publication time	Sun, 24 May 2026 13:52:29 +0000
Retrieval time	2026-05-24T14:02:32.695Z
Last seen	2026-05-24T14:02:32.695Z
Headline source	Publisher (no WeSearch rewrite)
Excerpt source	publisher body
Excerpt method	First ~120 words (~800 chars) of extracted publisher body, fair-use limited.
Summary	WeSearch · cerebras-chat (WeSearch summarizer)
Summary source text	contentText
Citation coverage	Summary is a WeSearch-generated derivative; primary citation is the original publisher URL.
Cluster	L8Z2ZVZDh28V
Cluster logic	Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison.
Ranking reason	Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking.
Publisher visit	Yes — open original
Substitutes article?	No — link-out required for full text

Rights status (four layers)

Publisher-declared

No publisher-confirmed rights record for this source yet.

Machine-readable

No source-specific machine-readable restriction detected beyond the public feed.

WeSearch interpretation

WeSearch declared handling (basis: Derived from the published RSS/Atom feed). This is WeSearch policy, not a legal grant on the publisher's behalf.

Unknown

Retrieval and training permissions are not asserted unless the publisher confirms them.

WeSearch handling by dimension

Indexing	May the item be indexed (stored, ranked, made findable)?	Allowed
Snippet	May a short excerpt of the publisher's text be shown?	Allowed
AI summary	May WeSearch generate its own short summary of the article?	Limited
Retrieval / RAG	May the content be exposed for third-party retrieval-augmented generation?	Not asserted
Model training	May the content be used to train AI models?	Not asserted
Commercial reuse	May the content be reused commercially?	Not permitted

Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.

Open original publisher → Source rights JSON → Machine-readable provenance → Rights framework → WESEARCH-STORY-PROVENANCE-V1

Opening excerpt (first ~120 words) tap to expand

From Azure to One VPS: How LLMs Made Migrating My Whole Side-Project Estate a No-Brainer Posted May 24, 2026 By Victor A 7 min read For years my side projects lived on Azure. App Services here, a Static Web App there, a managed SQL database, a sprinkle of Functions, some blob storage, a Communication Services resource for email. Each one made sense the day I created it. Added up over a dozen-plus projects, it became a sprawling estate with a monthly bill that kept quietly creeping — and a mental tax every time I opened the portal and saw resource groups I half-remembered. This month I moved all of it onto a single VPS. Every API, every static site, every Blazor app, the databases, the object storage, even the transactional email. Azure now shows zero resource groups.

…

Excerpt limited to ~120 words for fair-use compliance. The full article is at Victor A.

Anonymous · no account needed

Discussion

0 comments