Trust and security
Your logs stay in your accounts. Here is how we work inside them.
What your security, procurement and legal teams will ask, answered before they ask: access, credentials, where your data lives, AI, exit, and your security review.
01Your data
Three copies, in accounts you own by default.
Your logs stay in accounts you own, on premises or in your cloud: the SIEM, the lake and the raw archive. If you would rather we run the proof or the pipeline in Logmetry’s cloud account, we do, under the security and contract terms your legal and procurement teams set. Your choice.
Your sources
Firewalls, DNS, endpoints, cloud services
Pipeline, in your environment
Reduce, mask, enrich, route
Your destinations
Your SIEM What detection needs
Your lake Clean copy for AI and replay
Your archive Full raw copy for audit
Logmetry sees pipeline configuration, health metrics, and the samples we test with, all inside your environment. Unless you ask us to run it in our cloud account, we keep no copy of your logs on our systems.
Where it sitsThe pipeline runs in your data center or your cloud account, in the region you choose. The lake and the raw archive are storage in your own account.
If you would rather we run itThe proof or the pipeline can run in Logmetry’s cloud account instead, under the security and contract terms your legal and procurement teams set. We show you both before you choose.
AIPhase 1 puts none of your data into any AI model, except the AI comparison in the proof, and only if you ask for it: sample alerts, on a model you approve, in your own account. When you add AI triage later, the agent reads the lake copy read-only, runs on a model you approve in your own account, and a person on your team reviews every exception before anything changes. Your data never trains any model, ours or a vendor’s.
02Access and credentials
Minimal, named access you grant, log and take back.
We work inside your accounts under your controls, and every change we make is code your team approves.
Access you grant
- A named account for each of us, never a shared login, protected by multi-factor authentication.
- Read-only by default. Write access only where the build needs it, scoped to the pipeline, and removed at handover.
- Every change arrives as code that your team reviews and approves through your own change process.
- Everything we do runs under your logging, so your team can see what we did and when.
- Access ends on the last day of the engagement, and we confirm it in writing.
Credentials
- Secrets stay in your secret store. We never copy keys, tokens or passwords to our machines, to email or to chat.
- Where a system needs a credential, it reads it at run time from your store.
- We prefer short-lived, federated access to standing keys, and ask for it first.
- If a credential is ever exposed, we tell you at once so you can rotate it.
- 1Architecture reviewNo access at all. We work from your diagrams and your volumes.
- 2DiscoveryRead-only, through named accounts you create and can see in your logs.
- 3Proof of value and buildWrite access scoped to the pipeline. Every change is code your team approves.
- 4HandoverOur accounts closed and our access removed, confirmed to you in writing.
How we run our own house
- Our own cloud runs in separate AWS accounts for production and non-production.
- It is deployed only through a pipeline with no long-lived credentials anywhere, and production changes need a person’s approval.
- Root accounts carry multi-factor authentication, and our storage is encrypted with keys we manage.
- We apply the same habits in your environment that we apply in ours.
03Exit and continuity
Yours to keep, whoever runs it.
Everything we build is yours as code, so leaving us, or losing us, costs you a handover, not a rebuild.
What you own
- Every pipeline, route and rule, as code in your repository.
- The deployment, the tests and the monitoring, as code beside it.
- Runbooks for the tasks your team will do, and a written record of every design decision and the reason for it.
- All of your data, in your SIEM, your lake and your archive.
- Everything we build for you, under your ownership from the day it is delivered.
If we cannot continue
The design removes the dependency on us: nothing we build needs us in order to keep running.
- The lead architects named as key personnel in the contract.
- If Logmetry is acquired or its ownership changes, you get notice and the right to end the contract without penalty.
- The code and the runbooks in your repository are written so that the platform vendor’s own professional services, or any qualified partner you choose, can take over from them.
If you leave. Leaving us is a handover session, not a project. There is no Logmetry software in the design to license or remove. You keep a working, documented deployment, supported by its vendor under your subscription, and you can stop at the acceptance point of any phase.
04Who we are
The facts procurement checks first.
By default the design keeps your data inside your environment, under the controls you already audit. We sign your data processing agreement or your integrator’s, and answer your security questionnaire in full, with the evidence behind each answer.
- Legal name
- LOGMETRY LLC
- Entity
- New Jersey limited liability company
- Formed
- 23 March 2026. The founders’ experience is older than the company.
- Industry code
- NAICS 541512, computer systems design services
- People
- Our lead consultants and architects lead and oversee every engagement. Senior engineers in telemetry engineering, pipeline design and agentic AI, who worked in Fortune 500 and enterprise environments, build under their direction. No subcontractor works on your project without your written consent.
- What we do
- Design and build telemetry pipelines that sit in front of your SIEM, never in place of it. Are we a reseller? Yes, for certain vendors’ software. We are also the delivery partner and integrator on custom projects, directly or alongside your systems integrator. The pipeline subscription is in your name, bought from the vendor, its channel or through Logmetry where we resell it, and priced on its own line. We recommend what fits your business problem, even when that means changing nothing, and no SIEM or APM vendor pays us to recommend it.
- Markets
- The United States, and Mexico and Latin America.
- Tax forms
- W-9 and certificate of formation on request, the same day.
How you can buy from us
- Direct, on a short master agreement with a statement of work for each phase.
- Through your systems integrator’s paper, with Logmetry as its subcontractor on back-to-back terms. Your lawyers negotiate once, with a supplier already on your register.
- The pipeline subscription is in your name, bought from the vendor, its channel or through Logmetry where we resell it, and priced on its own line.
Day two
Logmetry designs and builds it: our lead architects lead every engagement, and senior engineers build under their direction. Day two is run by your own team, or by Logmetry if you want that. After-hours cover comes with every engagement, from your systems integrator or Logmetry, with the response window in the statement of work. The pipeline vendor supports its own software, under your own subscription.
05Questions
The security questions, answered before you ask.
Do you need access to our systems for the review?
No. The architecture review needs your diagrams and your volumes, nothing else. Read-only access starts at discovery, through named accounts you create.
Does any of our log data leave our environment?
Only if you choose it. Your logs stay in accounts you own, on premises or in your cloud: the SIEM, the lake and the raw archive. If you would rather we run the proof or the pipeline in Logmetry’s cloud account, we do, under the security and contract terms your legal and procurement teams set. Your choice.
Is our data used to train AI?
No. Phase 1 puts none of your data into any AI model, except the AI comparison in the proof, and only if you ask for it: sample alerts, on a model you approve, in your own account. When you add AI triage later, the agent reads the lake copy read-only, runs on a model you approve in your own account, and a person on your team reviews every exception before anything changes. Your data never trains any model, ours or a vendor’s.
How do you get through our security review?
By default the design keeps your data inside your environment, under the controls you already audit. We sign your data processing agreement or your integrator’s, and answer your security questionnaire in full, with the evidence behind each answer.
What happens if Logmetry disappears?
Everything we build is yours as code, so leaving us, or losing us, costs you a handover, not a rebuild. Nothing we build needs us in order to keep running, and the platform keeps its own vendor support under your subscription.
Who runs it after go-live?
Logmetry designs and builds it: our lead architects lead every engagement, and senior engineers build under their direction. Day two is run by your own team, or by Logmetry if you want that. After-hours cover comes with every engagement, from your systems integrator or Logmetry, with the response window in the statement of work.
Can we buy through our integrator?
Yes. Direct, on a short master agreement with a statement of work for each phase, or through your systems integrator’s paper, with Logmetry as its subcontractor on back-to-back terms. The pipeline subscription is in your name, bought from the vendor, its channel or through Logmetry where we resell it, and priced on its own line.
See your architecture drawn, with the costs, before you spend anything.
Our lead architects draw your SIEM feed from your diagrams: where the cost sits, what step one would change, and where it would not pay. If it pays, the next step is a two-week proof on your noisiest source.
Free. No system access. No obligation. You keep the drawing.
What you get
- Your architecture today, drawn
- The waste map
- Costs before and after, with estimates
- Your target architecture
- Options for your business problem
What it costsNothing