TheLunarEngine is a software company that automates systems. We implement the software you already run, or set up a new system from scratch, so work moves from request to decision to completion.
The route is where we begin. Either one can fit any engagement tier when the scope fits.
A process and integration map, configured system, working adapters and automations, tested migration where needed, and operating notes.
Architecture and data model, workflow services and APIs, scoped web or mobile interfaces, integrations, tests, and a rollout and support plan.
Not sure which applies? How we choose a route.
An illustrative engine line: the exact products and data paths depend on your environment.
in
Form, email, or an event from a product you already run.
core
Ownership, permissions, retries, and an audit record for every change.
adapters
Work items through REST APIs and webhooks, run by Node.js services.
out
A controlled database, notifications, and the task views each team needs.
Each capability ends in an operating result your team can see, not just a deliverable.
We connect the systems you already run and automate the hand-offs between them.
A request creates the right work item, survives duplicate events, and shows failures to an owner.
Secure internal tools and dashboards shaped around how your teams actually work.
A shared case view gives each role the decisions, records, and status they need.
React Native apps for iOS and Android that extend your workflows to people in the field.
Field staff can capture tasks and records on iOS or Android, with local storage when the scope requires it.
Well-modeled databases and pipelines that keep sensitive data accurate and controlled.
Source records are mapped, reconciled, and available for controlled reporting.
We stay with the system after launch: monitoring, fixes, and planned improvements.
Owners see API and job health, get alerted before users notice, and ship fixes through a controlled release path.
The proposal names the actual system, deliverables, owners, and acceptance points.
Process and integration maps, the agreed scope, and the decisions to validate.
Configuration or working software, the access model, APIs, data mappings, and tests.
Migration reconciliation where needed, a phased rollout, and user training.
Runbooks, alerts, operating documentation, support ownership, and the next changes.
Three typical shapes, from one workflow to a multi-department program. We recommend one after discovery and confirm scope in a written proposal.
One process, solved end to end, with a limited set of integrations.
$1,500 – $2,000
USD. Scope confirmed in a written proposal.
Best forA single team with a clear, painful process
Start with one workflowMultiple workflows, roles, and data sources on shared foundations.
$2,500 – $5,000
USD. Scope confirmed in a written proposal.
Best forDepartments replacing several disconnected tools
Discuss your platformA multi-department rollout with governance and long-term support.
From $5,000
USD. Custom proposal after discovery.
Best forOrganizations standardizing workflows across departments or regions
Plan a programA system is only as good as its release path and how fast someone knows it is failing. Every system we hand over comes with these practices, using the platforms that fit your stack.
Every change gets a Vercel preview your team can try before it ships; production releases are promoted, not rebuilt, and roll back in one step.
Sentry watches errors, slow endpoints, and scheduled jobs, ties each issue to the release that caused it, and alerts the owner.
Access is enforced in the data layer with PostgreSQL row-level security (managed on Supabase when it fits), behind a validated, rate-limited API.
Release notes on Substack keep stakeholders informed, so a change is announced before anyone stumbles on it.
No system can promise to be immune to attack. We reduce the attack surface, detect problems early, and make recovery routine. See how we design alerts.
Yes. We map the process, review what its APIs and permissions support, configure it, and build the connections and operating notes around it.
We design for retries, duplicate events, visible permanent failures, alerts, and a recovery owner. The exact controls depend on the source system.
Yes. A focused scope proves the handoffs and data model before a broader rollout.
You do. We hand over the code or configuration, documentation, and runbooks, and agree a support plan if you want us to keep running it with you.
Engineering notes from our journal: the conventions behind every system we hand over.
Tell us what you run today, where work stalls, and which teams need the result. We will help shape the route and the scope.