Least privilege, always
An employee gets scoped, approved access to the systems its role needs. Nothing else is reachable, whether or not it asks.
Security & Compliance
You are handing us your codebase. Here is exactly what happens to it.
An AI employee with real access to real systems is only acceptable if the boundaries are real too. This page is the whole picture: what an employee can reach, what it can never do without a human, what we encrypt, where our compliance programs actually stand, and how to reach us if you find a hole.
The principle
Automation should increase trust, not spend it.
Most of the risk in autonomous engineering is not the model. It is the blast radius: what the thing can touch, and whether anyone can reconstruct what it did afterwards. EdgeX11 is built around three answers to that.
A human on the sharp edges
Production, security, infrastructure, and anything a customer will read stops and waits for a person to approve it.
Everything is recorded
Every action, every approval, every refusal is logged and attributable, so “why did it do that” is always an answerable question.
Human control
Where the line sits.
This is not a setting you have to remember to switch on. It is how the product works.
AI executes
- Read code, tickets, docs and past incidents
- Investigate, plan and write changes
- Run tests and CI pipelines
- Open pull requests for review
- Deploy to non-production environments
- Draft updates, summaries and postmortems
Humans approve
- Production deployments
- Security-sensitive changes
- Infrastructure changes
- Customer-facing messages
- Granting an employee new system access
- Anything outside an employee’s defined role
Approval is a record, not a click
When an employee asks for approval, the request, the diff, the reasoning, the approver and the decision are all captured together. Months later, that is the answer to an auditor’s favourite question — not what you did, but why, and who agreed.
Platform
How the platform is built.
The controls underneath every plan, including the free one.
Encryption in transit
TLS 1.2+ everywhere, HTTPS-only with HSTS, and HTTP redirected to HTTPS at the edge.
Encryption at rest
AES-256 across every data store that holds your code, documents or organizational memory.
Per-tenant isolation
Each organization is its own tenant. Operational data and the memory graph are isolated, and every request is authorized against the tenant it belongs to.
SSO and SAML
Sign in with Google, Microsoft, Apple or enterprise SAML, so account lifecycle stays in your identity provider where it belongs.
Role-based access control
Owner, Admin and Developer roles govern who can hire employees, grant access, and approve changes.
Secrets stay out of memory
Credentials live in a broker backed by a managed secrets store. They are never written into an employee’s memory or knowledge graph, so memory can’t leak them.
Full audit trail
Every action an employee takes is logged, attributable and reviewable end to end.
Hardened infrastructure
Runs on AWS with managed Postgres, private networking, and services that hold no durable state they don’t need.
Private deployment
On Enterprise, run EdgeX11 in your own cloud account on dedicated infrastructure, with your own AI model if you prefer.
Your data
What we do with what you give us.
We don’t train on your code
Your code, documents and organizational memory are used to do your work. They are not used to train shared models, and they are not pooled with another customer’s. The whole promise of EdgeX11 is that your knowledge stays inside your company — that promise would be worthless if we mined it.
Your memory belongs to you
Everything your employees learn about your systems, decisions and incidents lives in your organizational memory, isolated to your tenant. You can inspect it, correct it, and take it with you. It follows you between plans and it does not evaporate if you leave.
Model providers are configurable
EdgeX11 supports multiple LLM providers, and on Enterprise you can bring your own model or run against an endpoint in your own account. That means the question “which third party sees this prompt” has an answer you get to choose.
Data residency and deletion
Tell us your requirements and we will tell you plainly whether we can meet them today. For deletion requests, see the Privacy Policy or write to us and we will action it.
Compliance
Where we actually stand.
Stated honestly, because you are going to check anyway and a vendor that rounds up here will round up everywhere else too.
Standards & compliance
- SOC 2 Type IIIn progress
- ISO 27001In progress
- GDPRAligned
- HIPAAReady
- AWS InfrastructureSOC 2 / ISO 27001 certified
“In progress” means the program is underway and not yet certified. We will not describe it as anything else until an auditor says so. The AWS infrastructure EdgeX11 runs on is itself SOC 2- and ISO 27001-certified, which is a different claim and we keep the two separate on purpose. Ask us for the current status, our security documentation, or what we can commit to contractually today.
Subprocessors
Who else touches the data.
The providers involved in running edgex11.com and the EdgeX11 product. We keep this current and will tell you before it materially changes.
| Provider | Purpose | Applies to |
|---|---|---|
| Amazon Web Services | Hosting, compute, managed database, object storage and content delivery | Website and product |
| LLM providers | Model inference for AI employees. Configurable per organization; Enterprise can bring its own model or endpoint. | Product |
| Stripe | Payment processing for paid plans. Card details go to Stripe, never to us. | Product (paid plans) |
| Web3Forms | Delivers website contact form submissions to our inbox | Website |
| Google Analytics | Website usage measurement, loaded only after you accept cookies | Website |
Scroll the table sideways on a narrow screen.
This website
Even the marketing site is locked down.
Not because a brochure is high risk, but because it is the cheapest possible signal of whether a vendor bothers.
- HTTPS only, with HSTS and HTTP → HTTPS redirection at the CDN
- A strict Content Security Policy served as a response header, not just a meta tag
- Clickjacking protection (
frame-ancestors 'none') and MIME-sniffing protection - A restrictive Referrer-Policy and Permissions-Policy
- No non-essential cookies until you accept them, and no advertising or cross-site trackers
- Static hosting with no server-side application to compromise
Responsible disclosure
Found something? Tell us.
We would much rather hear it from you than read about it later.
-
1
Email us
Send the details to admin@edgex11.com with “Security” in the subject. Include steps to reproduce and anything that helps us confirm it.
-
2
We acknowledge
We aim to confirm receipt within two business days and will keep you updated on what we find and when we expect to fix it.
-
3
We fix, then you publish
Please give us reasonable time to remediate before disclosing publicly. We will credit you if you would like to be credited.
-
4
Ground rules
Don’t access, modify or exfiltrate data that isn’t yours, don’t degrade the service for other users, and don’t social-engineer our people. Testing in good faith within these rules is welcome.
Security FAQ
The questions security reviews always ask.
Do you train models on our code?
No. Your code, documents and organizational memory are used to do your work, not to train shared or third-party models, and they are never pooled with another customer’s data. Your memory is isolated to your tenant.
Can an AI employee deploy to production by itself?
No. Production deployments, security-sensitive changes, infrastructure changes and customer-facing messages all require explicit human approval. The employee prepares the change and asks; a person decides. Both the request and the decision are recorded.
What access does an employee actually have?
Only what you grant, scoped to its role, least-privilege by default. Credentials are held in a broker rather than stored in the employee’s memory or knowledge graph, so its memory cannot leak a secret even in principle.
Are you SOC 2 or ISO 27001 certified?
Not yet — both programs are in progress, and we would rather tell you that than imply otherwise. EdgeX11 runs on AWS infrastructure that is itself SOC 2 and ISO 27001 certified, and our practices are GDPR-aligned. Contact us for current documentation and status.
Can we run EdgeX11 inside our own cloud?
Yes, on Enterprise. Private deployment puts EdgeX11 in your own account on dedicated infrastructure, with the option to bring your own model, so neither code nor memory leaves your environment.
How is one customer’s data separated from another’s?
Every organization is a distinct tenant. Operational data and the organizational memory graph are isolated per tenant, and every request is authorized against the tenant it belongs to. There is no shared memory between customers.
How do we report a vulnerability?
Email admin@edgex11.com with “Security” in the subject. We aim to acknowledge within two business days. See responsible disclosure above for the ground rules.
Next step
Send this page to your security reviewer.
Then ask us for whatever it doesn’t cover. We would rather answer a hard question early than lose your trust later.
No credit card required. Nothing ships without your approval.