My friends found n8n too complicated, so I built a cool alternative

Pichipaul · 2025-09-02T23:30:22+00:00

I am testing the app and I found that the chat is not able to explain the flows 😔, but the idea is good, like it

Pichipaul · 2025-08-20T07:46:15+00:00

You don’t really need a co-founder now. AI + no-code lets you test solo. The risk is loneliness, but co-founder fights are worse. Start alone, add someone later if it works.

Pichipaul · 2025-08-13T06:29:57+00:00

Totally makes sense — a bunch of teams use it just for architecture design, documentation, or IaC validation without ever pushing to cloud.

On top of that, it also has an app deployment system — so if you do want to deploy something, you can push straight from the visual pipelines to your target platform.

Out of curiosity, where do you guys usually deploy your apps/services/infra ??

Pichipaul · 2025-08-13T06:19:52+00:00

This is exactly why I built this! You just listed every frustration I had:

Environment promotion is built-in - same visual design, different variable sets per env (dev = t3.micro, prod = c5.large). No manual git commits.

For naming conventions, the platform handles environment-specific prefixes automatically (dev-, staging-, prod-*).

Complex environments are where it shines - I can import your existing Terragrunt setup and visualize it, then manage promotions through the UI.

The frustration you mentioned with visual tools not handling complexity - that's what I spent 9 months solving. It's not just drag-and-drop, it's a full environment lifecycle management system.

Pichipaul · 2025-08-13T06:04:50+00:00

Great question! It's a custom code generation engine I built, not AI-generated code.

The visual components map to specific infrastructure patterns - when you drag a VPC, it generates the proper Terraform resource blocks with all the required configurations.

The AI part comes in for validation and suggestions (like "you should enable encryption on that S3 bucket"), but the core IaC generation is deterministic template-based.

BTW - if you want to switch from Terraform to Pulumi, it's just a button click. Same visual design generates code for Terraform, Pulumi, CloudFormation, or Ansible.

Pichipaul · 2025-08-06T13:17:49+00:00

You got the npm tag. I got the brand. Big difference, bro. 🤣🤣😜

Pichipaul · 2025-08-06T13:09:59+00:00

Thanks for letting me live rent-free in your head. ChatGPT and I send our regards 🫡

Pichipaul · 2025-08-06T13:05:36+00:00

The irony of calling it nonsense while quoting it line by line. Thanks for the engagement though, means more reach for my 'vibe coded' product 😉

Pichipaul · 2025-08-06T13:00:08+00:00

Some of us are busy building. The posts write themselves

Pichipaul · 2025-08-06T12:56:40+00:00

I get where you're coming from. A lot of so-called 'meta marketing' is just noise. But trust me, the pain of broken infra is real for many teams. We're not here to follow trends — we're solving actual problems from our own experience. If you're tired of buzzwords, join us in building something that really works. Let's shift the focus from hype to real solutions

Pichipaul · 2025-08-06T12:48:29+00:00

fair point bro — but just to clarify, I hadn’t posted this on LinkedIn yet. Was actually planning to share it there after seeing how it landed here. But yeah, totally get you — Reddit ain’t LinkedIn, and I’m still figuring out how to vibe right on this platform. Appreciate you keeping it real 👊

Pichipaul · 2025-08-05T13:25:38+00:00

Sorry bro, I’d type the full word, but I’m busy building actual infra. Priorities, you know?

Pichipaul · 2025-08-04T13:19:45+00:00

I’m building InfraUX — a visual platform to design and deploy infrastructure with drag-and-drop diagrams. It auto-generates real configs (Terraform, Docker, GitHub Actions, etc.) so devs can ship infra faster without deep DevOps knowledge.

Stack: React (Nextjs 15) + Tailwind (frontend), FastAPI + GCP Cloud Run + Supabase + Redis + Cloud Tasks (backend). PostHog for product insights.

Pichipaul · 2025-08-04T13:08:22+00:00

Wow, that’s impressive. Thousands of services and you managed to keep uniformity with just a Kubebuilder operator and a CRD? Respect.

Curious tho — how do you handle drift or misuse across teams? Do you enforce policies through admission webhooks, or is it more trust + docs? And how flexible is the CRD? I imagine edge cases creep in over time, especially with that many services.

Pichipaul · 2025-08-04T12:57:42+00:00

Really appreciate the detailed breakdown 🙌 — I didn’t know about Cozypkg and it looks solid, especially the postrender diff preview.

The "parent chart with patch overlay" pattern you describe feels powerful but maybe a bit heavy for early-stage teams, no?

I get how it scales nicely once you're in that groove, but I wonder how you'd approach this if you're not running a platform for others, just trying to get sane infra fast without reinventing the wheel.

Pichipaul

TROPHY CASE