3 ms·
Show HN: Apcher – Generate self-hosted Node.js workflows from prompts
- indigodaddy 8mo agoInteresting concept. Is it open source if one would rather self-host it?
- Samueedwards1 8mo agoApcher generates proprietary Node.js code you own and self-host ($59/workflow). Think "Cursor for backend workflows" — prompt → production ZIP with Watchdog/CI/etc. baked in. Generator stays at apcher.dev; output = yours forever, no license restrictions beyond standard use. No success tax—you run it 1M times on your infra.
- indigodaddy 8mo agoSo that's a no on open source right?
- Samueedwards1 8mo agoCorrect—no open source. $59/workflow → production Node.js you own completely (no license restrictions, run 1M times anywhere). Full export, no host, time, or execution fee. Output = yours forever.
- guerython 8mo ago[flagged]
- Samueedwards1 8mo agoGreat question—we treat generated code as production code too. Secrets/Env: - `${{ secrets.YOUR_SECRET }}` GitHub Actions syntax throughout - `.env.example` + docker-compose.yml with all expected vars - No hardcoded values; all externalized Proving it works: - Built-in fixture tests (`npm test`) for every integration point - `npm run apcher:full-scan` catches CVEs + dep issues pre-ZIP - Watchdog generates synthetic drift tests that run on startup - Idempotency baked in (safe to retry 1K times) Example ZIP includes Stripe test mode keys + Postgres docker fixture.
- Samueedwards1 8mo agoApcher turns "GitHub repo + Slack workflow" → production Node.js ZIP you own. Includes: - Express server + full routes - Watchdog (API drift detection, CVE scans via npm run apcher:full-scan) - Retries, idempotency, peter-evans/create-pull-request@v6 for auto PRs - `npm install && npm start` ready $59/workflow. No subs, deploy anywhere. Try it: apcher.dev Give me you feedback
- Samueedwards1 8mo agomy-workflow/ ├── package.json ├── apcher.lock ├── .env.example ← all secrets documented ├── scripts/ ← Express server + routes ├── github/ ← integrations └── README.md$ unzip && npm i && npm start = production server live. `npm run apcher:full-scan` catches CVEs + deps upfront.
- Samueedwards1 8mo agoHey HN — Here’s the exact intent I tested with Apcher.dev Stripe customer.subscription.created → verify → idempotency → Postgres → provision workspace → SendGrid → Slack → monitoring. Once expanded to production-safe logic, it became 19 steps. First 6: Verify webhook signature (STRIPE_WEBHOOK_SECRET) Extract event.id, subscription.customer, price.id Ensure price.id === pro_annual_price_id Check processed_events for event.id Insert event.id before side effects Fetch full customer via Stripe SDK Snippet: Js id="j3m4zl" if (!Stripe.verifyWebhookSignature(req.body, signature, process.env.STRIPE_WEBHOOK_SECRET)) { return { success: false, error: 'Invalid webhook signature' }; } const [existingEvent] = await PostgreSQL.query( 'SELECT * FROM processed_events WHERE id = $1', [eventId] ); if (existingEvent) { return { success: true, message: 'Event already processed' }; } Generated structure: Id="s2x9pq" my-workflow/ ├── integration.js ├── scripts/ ├── .env.example ├── apcher.lock ├── github/ └── README.md The surprising part wasn’t the API calls — it was how much production scaffolding each “simple webhook” really needs. Curious how others here handle idempotent webhook pipelines in production.
- Samueedwards1 7mo agoDistributed systems are fragile. We spend 40% on plumbing (retries, idempotency, state mgmt). Current "Solution": Rent proprietary runtimes. Swap plumbing for vendor lock-in + exec tax. Apcher: Generate resilience directly into your Node.js repo. Atomic SQL, native retries, Watchdog drift PRs. $0 exec fees. Full export—deploy anywhere, run locally, live in your repo. Who's brittle today?
- Samueedwards1 7mo agoPayment workflows die silently. Here's what ships before yours burns money: Raw Stripe → 3x retries + idempotency + conflict DOs + rollbacks. Apcher injects resilience into your Node.js repo. Try it for free. Test chaos locally. What broke your last payment flow? apcher.dev