About
Durable background jobs, built from Lalitpur, Nepal
Nodeflux is a developer-tools startup focused on background jobs and workflow orchestration for backend teams who'd rather not build retry logic and queue infrastructure themselves.
Lalitpur
Headquartered in Nepal
Usage-based
Pricing, always
Direct
Access to the team, not a queue
No DSL
Jobs are just functions
Our story
Why we started Nodeflux
Every backend eventually needs background jobs — sending email, processing uploads, syncing data on a schedule. Most teams build this themselves on top of a raw queue, and end up rebuilding the same retry logic, idempotency checks, and dead-letter handling every time, slightly differently, with slightly different bugs.
Nodeflux exists so that work doesn't get repeated. Background jobs, scheduling, and retries as a primitive you import, not a system you maintain. What started as infrastructure for a few early projects out of Lalitpur is now used by teams building well beyond Nepal.
We're deliberately staying small in scope for now — one product, done properly, rather than a dozen half-finished ones. The roadmap is driven by what the people actually using Nodeflux run into, not by a feature checklist copied from a larger competitor.
How we work
From signup to production, without a sales cycle
01
Write a job
Define a job as a plain async function with the Nodeflux SDK — no YAML, no separate workflow language.
02
Deploy it
Deploy it alongside the rest of your app. Nodeflux discovers registered jobs automatically on deploy.
03
Trigger & observe
Trigger it from an event, a webhook, or a schedule, then watch every run, retry, and step in the dashboard.
What we believe
A few principles that don't change as we grow
Functions, not a new DSL
Jobs are plain functions deployed with the rest of your app — no YAML workflow language to learn and maintain separately.
Idempotency as a first-class concept
Retries shouldn't duplicate a charge or a sent email. Idempotency keys are part of the step API, not something you bolt on yourself.
Observability by default
Every run is logged automatically — input, output, and timing per step — not an integration you wire up after something breaks.
Usage-based, always
You pay for runs that happen, not reserved capacity sitting idle. Standard pricing is never hidden behind a sales call.
Frequently asked questions
Common questions about Nodeflux
Is Nodeflux a Nepali company?
Yes. Nodeflux is a developer-tools startup founded and based in Lalitpur, Nepal.
Who is Nodeflux built for?
Backend teams who need reliable background jobs and scheduling without standing up and operating their own queue infrastructure — from solo developers to small production teams.
How is Nodeflux different from rolling your own queue?
You could build retries, idempotency, and step checkpointing yourself on top of a raw queue — most teams do, and most of those implementations have gaps. Nodeflux gives you that as a primitive instead of a project.
Do I need to talk to sales to get started?
No. You can sign up and deploy your first job without a sales call. The team is available if you want to talk through a migration or a larger setup first.
How big is the Nodeflux team?
Nodeflux is a small team based in Lalitpur. That means slower feature velocity than a VC-funded platform with dozens of engineers, but it also means the person who answers your support email is someone who wrote the code.
What's next for Nodeflux?
More runtimes beyond TypeScript and Python, a self-hosted option for teams that need it, and deeper observability — roughly in that order, driven by what early users actually ask for.