Skip to main content
Five official language integrations

Bring every scattered script under one roof.

See, start, stop and troubleshoot background work across applications and machines from one protected console. Workers connect out; they never need an inbound port.

WORKERSsynced 2s ago
billing-jobsspring boot · 3 processesrunning
etl-runnernode.js · 1 processstopping
report-workerpython · 2 processesidle
inventory-syncgo · 2 processesfailed

Nobody knows what is running where.

A poller inside a service. A Node.js import script. A maintenance task only one engineer knows how to run. Synapsys leaves that work where it belongs and gives teams one consistent place to operate it.

Outbound by design

Workers use one authenticated heartbeat. Core never calls them, so applications need no new listener, ingress route or inbound firewall rule.

Logs with every run

Follow a process from start to finish and inspect its captured output in context, instead of searching across hosts after something fails.

Operate from any screen

The authenticated console adapts to desktop, tablet and mobile layouts, with touch-friendly navigation and entity views.

ADOPT, DON'T REWRITE

Wrap the work you already trust.

Your existing job keeps its own code. Extend the base class, declare whether it runs forever or runs once, and cooperate with the stop signal. The starter handles authentication, heartbeats, command tokens, lifecycle and execution output.

Follow the tutorial →
NightlySync.java
@SynapsysProcess(name = "nightly-sync")
public class NightlySync extends AbstractEndlessProcess {

@Override
protected void runForever(StopSignal stop) throws Exception {
while (!stop.isStopRequested()) {
reconcileInvoices();
Thread.sleep(5_000);
}
}
}

Point your first worker at a Core in five minutes.

Run the Core container, create a worker token, and add one published dependency. Spring Boot, Node.js, Python, Go, .NET, and direct HTTP integrations share one lifecycle contract. Check each manual for current package availability.