One collection layer
Bring supported streams into a common path, ready for the tools you use today and the ones you evaluate next.
THE INDEPENDENT DATA PATH
Collect once.
Keep your
options open.
Your logs shouldn’t tie you to one platform. Send them where you need them—and see the flow along the way.
In development. Early access conversations welcome.
ONE COLLECTION LAYERFLOW / 001
YOUR SOURCESYOUR DESTINATIONS
Servers
Endpoints
Applications
Mainline
SSIEM
OObservability
DData storage
One source. Multiple routes.Conceptual flow
01—03
Connect your sources.
Choose what comes next.
COLLECTION, WITHOUT THE DEAD END.
Keep the sourceChoose the destinationFollow the flowMEET MAINLINE
Know where your
data is going.
Collection, routing, and flow visibility in one place. See what’s arriving, where it’s being sent, and which streams need a closer look.
The sample environment shows failing destinations, making the affected routes visible alongside incoming source streams.
More destination freedom
Send the same stream to multiple platforms. Compare a new destination while keeping your existing route in view.
Less guessing
See when expected data stops arriving. Use source and delivery signals to narrow down where to investigate.
FOLLOW THE FLOW
A clearer path.
Even when it stops.
Add a destination. Spot an interruption. Explore how a visible data path changes the conversation.
ONE STREAM, TWO DESTINATIONS
Collect once.
Deliver in parallel.
A supported source feeds Mainline. The same stream follows two routes, each with its own destination.
Both routes are active in this example.
ILLUSTRATIVE EXAMPLE
Windows eventsSource collection
MainlineRouting
SplunkReceiving
ElasticReceiving
Delivery interrupted
A PRACTICAL REASON TO START
Your next platform change
starts at the source.
Try a new destination.
Keep collection in place.
Evaluate a second logging platform with a supported stream. Compare what arrives before deciding where to send it next.
Live data migration · Parallel evaluation
See the gap
before chasing the cause.
When expected logs disappear, start with the path. Identify the affected stream and use the available signals to guide investigation.
Flow visibility · Missing-stream investigation
Make the next
onboarding repeatable.
Start with one customer use case. Evaluate a shared collection and routing layer that fits your delivery and support process.
Customer onboarding · Joint pilots
A FEW GOOD QUESTIONS
Before you
connect.
Mainline is in active development. Early pilots start with a supported route and a specific problem to solve.
Does Mainline replace my SIEM or observability platform?
Mainline focuses on collecting and routing data, with visibility into its flow. Your destination platforms continue to handle their own analytics, investigations, and dashboards.
Can I move from Splunk to another destination?
The intended workflow keeps compatible source collection in place while you evaluate another destination. A pilot confirms the adapters, event formatting, and delivery behavior. Historical data, saved searches, dashboards, and detection rules need separate migration planning.
Which integrations are available?
The development views show syslog and configured destinations such as Splunk, Loki, and Wazuh. A configured destination does not establish successful delivery. Tell us the exact source and destination you need; availability and operating limits are confirmed for each pilot.
Will it tell me why a stream stopped?
Mainline makes the affected flow visible so you can narrow the investigation. The available source and destination signals determine how much the product can tell you. A quiet source and a failed delivery are different conditions.
How does an early pilot work?
Choose a supported source and destination, define the desired result, and agree on scope, price, assistance, and a review date. Test delivery and interruption visibility together before deciding on ongoing use.
LET’S START WITH YOUR DATA PATH
One source.
Your next possibility.
Have a destination to evaluate or a stream that’s hard to track?
Start with a focused Mainline pilot.
One use case. A clear definition of success.