Source: https://seerepo.com/compare/conductor-oss/conductor/vs/signalapp/Signal-Server
Markdown source: https://seerepo.com/compare/conductor-oss/conductor/vs/signalapp/Signal-Server.md
Description: conductor and Signal-Server share 8 technologies: s3, Redis, AWS S3, Google, sts, com.google.auth:google-auth-library-oauth2-http, org.slf4j:slf4j-api, and io.micrometer:micrometer-core. Both are written in Java.

# conductor vs Signal-Server

conductor and Signal-Server share 8 technologies: s3, Redis, AWS S3, Google, sts, com.google.auth:google-auth-library-oauth2-http, org.slf4j:slf4j-api, and io.micrometer:micrometer-core. Both are written in Java.

- [conductor-oss/conductor](https://seerepo.com/r/conductor-oss/conductor): Conductor is an event driven agentic workflow engine providing durable and highly resilient execution engine for applications and AI Agents
- [signalapp/Signal-Server](https://seerepo.com/r/signalapp/Signal-Server): Server supporting the Signal Private Messenger applications on Android, Desktop, and iOS

## What they share and what sets them apart

- In common: s3, Redis, AWS S3, Google, sts, com.google.auth:google-auth-library-oauth2-http, org.slf4j:slf4j-api, io.micrometer:micrometer-core
- Only in conductor: org.springframework.boot:spring-boot-starter-web, aws-java-sdk-sqs, java-nats-streaming, jedis, jnats, kafka-clients, mysql:mysql-connector-java, org.elasticsearch.client:elasticsearch-rest-client, org.mongodb:bson, PostgreSQL, redis-java, redisson, spring-boot-flyway, sqlite-jdbc, DataStax, Flyway, Postgres, com.github.ben-manes.caffeine:caffeine, org.apache.commons:commons-pool2, com.zaxxer:HikariCP, io.orkes.queues:orkes-conductor-queues, RabbitMQ, software.amazon.awssdk:sqs, MySQL, org.springframework.boot:spring-boot-starter-jdbc, SQLite, com.pgvector:pgvector, io.pinecone:pinecone-client, MongoDB, Elasticsearch, Kafka, Google Cloud Storage, graal-sdk, grpc-services, tomcat-embed-core, truffle-runtime, org.graalvm.polyglot:polyglot, React, React Router, react-router-use-location-state, Vite, react-router-dom, mkdocs-material, org.springframework.security:spring-security-core, Model Context Protocol, org.springframework.ai:spring-ai-model, spring-ai-bedrock-converse, spring-ai-client-chat, spring-ai-mistral-ai, spring-ai-ollama, software.amazon.awssdk:bedrockagentruntime, jsoup, tika-core, org.apache.pdfbox:pdfbox, com.vladsch.flexmark:flexmark-all, com.github.jknack:handlebars, bval-jsr, Spring, com.networknt:json-schema-validator, log4j-slf4j-impl, logback-classic, micrometer-registry-azure-monitor, micrometer-registry-cloudwatch2, micrometer-registry-prometheus, org.springframework.boot:spring-boot-starter-actuator, spring-boot-opentelemetry, spring-boot-starter-log4j2, org.apache.logging.log4j:log4j-api, com.netflix.runtime:health-api, org.apache.logging.log4j:log4j-core, @mui/system, classnames, MUI, reaflow, monaco-editor, React Hook Form, react-hotkeys-hook, jsonforms, @dnd-kit/core, react-data-table-component, recharts, use-gesture, react-container-query, monaco-languages-jq, react-datepicker, react-highlight, react-number-format, react-player, react-vis-timeline, TanStack, @phosphor-icons/react, @mui/icons-material, react-markdown, remark-gfm, prismjs, dom-to-image, highlight.js, @hookform/resolvers, yup, Ajv, ajv-errors, ajv-formats, cron-validate, @material-ui/styles, material-ui, @monaco-editor/react, Formik, dagre-d3, orkes-workflow-visualizer, react-vis-timeline-2, @use-gesture/react, D3, react-cron-generator, react-resize-detector, @material-ui/icons, prop-types
- Only in Signal-Server: JAX-RS, org.glassfish.jersey.core:jersey-server, apache-client, aws-crt-client, lettuce-core, software.amazon.awssdk:dynamodb, Stripe, Firebase, dropwizard-dependencies, jersey-common, jetty-ee10-bom, jetty-ee10-servlets, jetty-ee10-websocket-jetty-server, org.apache.tomcat:annotations-api, reactor-bom, reactor-core-micrometer, io.dropwizard:dropwizard-core, org.eclipse.jetty:jetty-bom, jakarta.servlet:jakarta.servlet-api, io.dropwizard:dropwizard-jersey, org.eclipse.jetty.websocket:jetty-websocket-jetty-api, io.dropwizard:dropwizard-jetty, jakarta.inject:jakarta.inject-api, io.dropwizard:dropwizard-http2, dropwizard-migrations, com.webauthn4j:webauthn4j-core, com.auth0:java-jwt, Apache, jakarta.validation:jakarta.validation-api, commons-logging, dropwizard-metrics, metrics-core, metrics-healthchecks, micrometer-bom, opentelemetry-logback-appender-1.0, org.apache.logging.log4j:log4j-bom, ch.qos.logback:logback-core, ch.qos.logback:logback-classic, ch.qos.logback.access:logback-access-common, io.micrometer:micrometer-registry-otlp, net.logstash.logback:logstash-logback-encoder, OpenTelemetry

## Side by side

| | conductor | Signal-Server |
|---|---|---|
| Size | 570,276 lines written, 2,315 code files | 168,448 lines written, 890 code files |
| Who writes it | 2.1% of its commits signed by AI. With Claude Code and Cursor | 0% of its commits signed by AI |
| Activity | Last push November 14, 2026, 4,769 commits, 32,471 stars | Last push November 4, 2026, 5,577 commits, 10,783 stars |
| Tests | 712 test files. 34.5% of its code files have a test that imports them | 369 test files. 72.6% of its code files have a test that imports them |

- Size: Lines written by people and agents, without generated ones; code files, without tests.
- Who writes it: A commit counts as AI's when it carries its signature: a Co-Authored-By line, its author name or the merge of its branch.
- Activity: From GitHub and its history, on the day SeeRepo read it.
- Tests: The files that test the code, and the share of code files a test imports.

## Frequently asked questions

### Which is bigger, conductor or Signal-Server?

conductor, with 570,276 lines written; Signal-Server has 168,448.

The proof: [conductor-oss/conductor's code at commit 1d268e4](https://github.com/conductor-oss/conductor/tree/1d268e4c9b0fe77c7122200dad5c60c61e94aa89)

### Which has more GitHub stars, conductor or Signal-Server?

conductor, with 32,471 stars; Signal-Server has 10,783.

The proof: [conductor-oss/conductor on GitHub](https://github.com/conductor-oss/conductor)

### Which has more tests, conductor or Signal-Server?

conductor, with 712 test files; Signal-Server has 369.

The proof: [conductor-oss/conductor's code at commit 1d268e4](https://github.com/conductor-oss/conductor/tree/1d268e4c9b0fe77c7122200dad5c60c61e94aa89)

### Which was updated more recently, conductor or Signal-Server?

conductor: its last push was on November 14, 2026, and Signal-Server's on November 4, 2026.

The proof: [conductor-oss/conductor's commits on GitHub](https://github.com/conductor-oss/conductor/commits)

### Which has more commits signed by AI, conductor or Signal-Server?

conductor: an AI signed 2.1% of its commits, with Claude Code and Cursor.

The proof: [the commits each tool signed in conductor-oss/conductor](https://seerepo.com/r/conductor-oss/conductor/ai)

## Sources

- conductor-oss/conductor: Read on November 14, 2026, at commit 1d268e4 (https://github.com/conductor-oss/conductor/tree/1d268e4c9b0fe77c7122200dad5c60c61e94aa89)
- signalapp/Signal-Server: Read on November 13, 2026, at commit 21be842 (https://github.com/signalapp/Signal-Server/tree/21be84230390a80bbf33a016a12a8ef4ab9863e7)

## What is your repo built with?

Any public repo, with no account: https://seerepo.com/r/owner/repo/built, with the owner and name it has on GitHub.