Skip to main content

Built for the engagements where trust is the requirement.

Published 2026-07-24 Updated 2026-11-12

The largest AI mandates come with the hardest questions — where the data lives, who can reach it, what an auditor sees three years later, and what happens when something fails. This page is the standing answer, and every claim on it is an engineering default we deploy, not an aspiration.

iSimplifyMe runs every regulated client's dedicated infrastructure in that client's own AWS account with IAM-scoped execution; shared platform services run on ours. Client data never trains public models, audit logs are retained for seven years, HIPAA-ready architecture ships with the AWS BAA on every PHI account, and iSimplifyMe claims no certification it does not hold. Case studies name a client only with its agreement; references are available under NDA.

How Is Client Infrastructure Isolated?

Between client accounts, isolation is enforced at the account perimeter, not at the application layer. Every regulated client's dedicated infrastructure runs in its own AWS account with IAM-scoped execution, so one client's deployment cannot reach another's by construction. Shared platform services (intake, the AI concierge, monitoring) run on iSimplifyMe's account, where multi-tenant systems key every record by tenant identity in the partition key, a pattern documented in Layer 5: Multi-Tenant Business Integration.

For the dedicated account, the perimeter is also the cheapest insurance an auditor can ask for — a cross-tenant finding cannot exist where there is no shared tenancy to cross.

What Happens To Client Data?

Foundation-model inference on client data runs on private AWS through Bedrock, with the data-retention mode pinned to zero where the model permits it. Client data never trains public models, never leaves AWS for a third-party AI API, and proprietary business logic remains the client's intellectual property — commitments we also publish in our AI Transparency disclosure. Data sovereignty and network sovereignty are engineering defaults on every deployment, not premium add-ons.

What Is The Compliance Posture?

Three facts, put the way an auditor would want them. No SOC 2 report: for a client's dedicated infrastructure, the controls an examination would test are visible in the client's own account; shared platform services run on ours. HIPAA-ready architecture is a default, with the AWS Business Associate Addendum accepted on every PHI account (per account, or organization-wide through AWS Artifact), iSimplifyMe's own BAA with the practice where we operate, and the full reference architecture published in our healthcare whitepaper. Audit logs are retained for seven years, so the answer to “what happened” outlives the engagement that produced it.

How Do You Prove What The System Did?

Reliability engineering is published, not promised. Deterministic quality gates block bad output before it ships — the model is never trusted to grade its own work — and post-deploy verification audits what actually rendered. Operational AI is investigate-only: agents detect, diagnose, and file tickets, and never remediate production on their own. Audit trails run end to end. The full architecture is in Layer 4: Reliability Engineering for Regulated AI — the same patterns every engagement inherits.

Who Are We Buying From?

iSimplifyMe was founded in 2011 and has operated continuously for fifteen years — bootstrapped, with no outside capital and no investor timeline shaping architecture decisions. The AI practice was not retrofitted onto the firm's earlier services stack: the systems we operate were built AI-native on private AWS Bedrock, with in-house model training on dedicated hardware and multi-agent orchestration running in production, and the reference architectures published in our whitepapers rather than asserted.

Vendor viability and technical provenance are both standard procurement questions — how long the firm has existed, and whether the capability being bought is native or retrofitted. Those are the answers, and they are checkable.

Can We Talk To Your Clients?

The roster names a client and its public work; a case study or a proposal names a client only with that client’s agreement. That is policy, not limitation: the engagements we take are the kind where confidentiality is part of the work. References are available under NDA in qualified engagements, our setup-type case studies document the same systems with production receipts, anonymized unless the client agrees to be named, and we participate in client security reviews and procurement processes as part of how engagements run.

Who Is Accountable For Security?

Joseph W. Elstner, Founder & Principal Architect, is iSimplifyMe's accountable security lead. He owns the security program for every system the firm builds or operates — the client sites on AWS, the platforms under isimplifyme.com, and the managed WordPress fleet — from incident response and vulnerability management to fleet-wide patching.

Security notices and vulnerability reports go to joe@isimplifyme.com. The same contact is published in machine-readable form at /.well-known/security.txt, the RFC 9116 vulnerability-disclosure file that scanners and researchers look for.

When a security questionnaire asks for one named owner who can be reached, this is the name that goes on the form.

Frequently Asked Questions

Is iSimplifyMe SOC 2 compliant?

No, and we do not claim it. iSimplifyMe holds no SOC 2 report and is not pursuing one: a regulated client's dedicated infrastructure runs in its own AWS account, so the controls a SOC 2 examination would test there — dedicated account perimeters, IAM-scoped execution, seven-year audit-log retention — are visible to the client's own security review directly. Shared platform services, intake and the AI concierge among them, run on iSimplifyMe's account. We publish that plainly rather than imply a certification we do not hold.

How is client infrastructure isolated?

A regulated client's dedicated infrastructure runs in its own AWS account with IAM-scoped execution, and shared platform services run on ours. Between client accounts, isolation holds at the account perimeter, not at the application layer, so a defect in one deployment cannot reach another client.

Does client data train AI models?

No. Foundation-model inference on client data runs on private AWS through Bedrock with the data-retention mode pinned to zero where the model permits it. Client data never trains public models, never leaves AWS for a third-party AI API, and proprietary business logic remains the client's intellectual property.

Is iSimplifyMe HIPAA-ready?

Yes — HIPAA-ready architecture is an engineering default, not an add-on. For healthcare engagements the AWS Business Associate Addendum is accepted on every account that handles PHI (per account, or once for an organization through AWS Artifact), iSimplifyMe signs its own BAA with the practice when it operates the environment, and the reference architecture for HIPAA-regulated deployment is published in our whitepapers.

How long has iSimplifyMe been operating?

Since 2011 — fifteen years of continuous operation, bootstrapped, with no outside capital. The AI practice was not retrofitted onto the firm's earlier services stack: the systems we operate were built AI-native on private AWS Bedrock, with in-house model training on dedicated hardware and multi-agent orchestration running in production, and the reference architectures published rather than asserted.

Who is responsible for security at iSimplifyMe?

Joseph W. Elstner, Founder & Principal Architect, is the accountable security lead for every system iSimplifyMe builds or operates — incident response, vulnerability management, and fleet-wide patching included. Security notices and vulnerability reports go to joe@isimplifyme.com, the contact also published at /.well-known/security.txt.

Can we speak to existing clients?

The client roster names clients and the public work iSimplifyMe built or operates for them. A case study names its client only with the client’s agreement; otherwise it documents the work as an anonymized, setup-type write-up with production receipts. References are available under NDA in qualified engagements.

Start The Conversation
Apex Architecture

Every site we build runs on Apex — sub-500ms, AI-native, zero maintenance.

Explore Apex Architecture
⌘ K