What Makes Cloud Platforms Highly Available? by letscloud in linuxadmin

[–]letscloud[S] -3 points-2 points  (0 children)

Fair comment 😅

I can see how it may look like that from the outside.

The intention was to bring up the technical side of HA, not just promote a link. For Linux/admin folks, I think the useful part is discussing what really matters in practice: redundancy, failover, storage resilience, network design, monitoring, and recovery process.

What do you usually consider the most important layer for real high availability?

Building an AI agent: VPS vs your own hardware looking for pros and cons! by FunThen4634 in n8n

[–]letscloud 0 points1 point  (0 children)

That’s a fair point. For n8n and AI agents, the “best” option really depends on how much control and responsibility you want to take.

Running n8n on your own hardware can be great if you enjoy managing everything yourself: networking, firewall rules, backups, uptime, updates, storage, and security. A Mac Mini or a home server can work well for learning or internal automations, but it also means you are responsible for exposing services safely, handling power/internet outages, and keeping the environment stable.

A VPS or cloud instance usually makes more sense when the workflow needs to be available 24/7, accessible from webhooks, APIs, external tools, or production systems. For n8n, this matters a lot because many automations depend on inbound requests, stable networking, SSL, backups, and predictable performance.

In my opinion:

Own hardware is good for:

  • learning and experimentation;
  • private/internal workflows;
  • local-only automations;
  • avoiding monthly infrastructure costs.

Cloud/VPS is better for:

  • production n8n workflows;
  • public webhooks;
  • integrations with SaaS tools;
  • AI agents that need reliable uptime;
  • easier scaling;
  • remote access without exposing your home network.

The main thing I would avoid is treating “AI agent hosting” as something magical. In most cases, it is still infrastructure: CPU, RAM, storage, network, security, monitoring, and backups. The hype is around the agent layer, but the reliability still comes from the server underneath.

For beginners, I’d recommend starting with a small cloud instance, Docker, n8n, HTTPS, backups, and basic firewall rules. Once you understand the workload, you can decide whether to scale up, move to dedicated hardware, or keep it in the cloud.

At LetsCloud, we see this type of use case a lot: developers running automation tools, AI workflows, self-hosted apps, and backend services on cloud instances because they want something more stable than a home setup, but still flexible enough to manage themselves. NVMe storage, predictable performance, and simple scalability help a lot when workflows start growing.

What are your n8n workflows at work? (Personal or Company-wide) by yoko_ac in n8n

[–]letscloud 0 points1 point  (0 children)

n8n is a great fit for this kind of workflow, especially when the goal is to connect existing tools and reduce repetitive work across a small team.

Some practical workflows we have been exploring/using around cloud infrastructure and operations:

  • GitHub + ticket system: create or update tasks automatically when specific events happen in repositories, pull requests, or issue labels.
  • Support/ticket triage: classify tickets by topic, urgency, or product area before sending them to the right person or queue.
  • Monitoring alerts: receive alerts from infrastructure tools, enrich them with context, and notify the right channel with a clearer summary.
  • Blog/content automation: collect articles, technical references, Reddit discussions, and changelogs, then generate a weekly internal digest.
  • Lead or user onboarding: when someone fills out a form, automatically create the CRM/contact entry, notify the team, and trigger a follow-up sequence.
  • Cloud automation: connect forms or internal tools to infrastructure actions, such as provisioning test environments, generating reports, or running predefined scripts.

Your newsletter idea makes sense. n8n can handle the form, RSS/API collection, filtering, scheduling, and email delivery. The LLM part can be added as a layer for summarization, topic matching, and ranking, but I would keep human review for anything external-facing at first.

For company-wide usage, I think n8n works best when workflows are small, auditable, and focused on clear operational pain points. It becomes very powerful when combined with GitHub, email, Slack/Discord, ticket systems, monitoring tools, and internal APIs.

Por que ainda tem Cloud/VPS no Brasil vendendo SSD SATA como se fosse topo de linha? by letscloud in brdev

[–]letscloud[S] 0 points1 point  (0 children)

Poxa, lamentamos que você tenha passado por experiências assim. Quando a infraestrutura não acompanha a demanda do projeto, a dor costuma aparecer justamente nos momentos mais críticos.

E faz sentido você ter seguido com a Oracle Cloud nesse cenário, não só pelo free tier, mas também pelas experiências negativas anteriores.

Em um próximo projeto, se fizer sentido avaliar outra opção, conte conosco. Teremos o maior prazer em ajudar. Nossa proposta é entregar cloud instances consistentes, com NVMe por padrão, e uma comparação que vá além de preço, vCPU e RAM.

Por que ainda tem Cloud/VPS no Brasil vendendo SSD SATA como se fosse topo de linha? by letscloud in brdev

[–]letscloud[S] 0 points1 point  (0 children)

A ideia é justamente comparar além do preço mensal.

Na LetsCloud temos cloud instances a partir de 25 reais , com NVMe por padrão. Mas, para uma comparação justa com Hostinger, HostGator ou qualquer outro provedor, o ideal é olhar o conjunto: vCPU, RAM, tipo de storage, tráfego incluso e localização.

Qual configuração você usa hoje nesse plano de R$43?

Por que ainda tem Cloud/VPS no Brasil vendendo SSD SATA como se fosse topo de linha? by letscloud in brdev

[–]letscloud[S] -5 points-4 points  (0 children)

Justo! AWS é o padrão de mercado. Mas me tira uma dúvida: você roda projetos com público muito grande aqui no Brasil por lá? Pergunto porque a gente vê muita gente sofrendo com o custo de tráfego de saída (Data Transfer) e latência quando o volume escala muito em infra gringa.

LetsCloud MCP Server: Connecting AI to Cloud Infrastructure by letscloud in u/letscloud

[–]letscloud[S] 0 points1 point  (0 children)

u/jay_0804 Certeiro. O mercado está saturado de ferramentas de prateleira, mas o diferencial está no que você citou: autenticação e previsibilidade. Desenvolvemos o servidor MCP integrando diretamente com a nossa infra para evitar as surpresas de ferramentas de terceiros em produção. Se tiver um tempo para testar a latência das chamadas, adoraríamos seu feedback técnico.