Frequently Asked Questions

No — the solution templates on this site are proof-of-capability demos, not off-the-shelf products. Each one shows a real pattern running in my own sandbox. The actual deliverable is that pattern implemented on your infrastructure, scoped to your environment through a Statement of Work.

Four steps: you inquire about a specific template → we have a discovery call to scope what it'd take on your actual infrastructure → I draft a Statement of Work → once signed, I build, test in your environment, and hand you the keys.

The general pattern (the template itself) stays my IP — I reuse it across clients. Everything built specifically on your infrastructure for your engagement, including any custom integration work, is yours. Documentation of the finished setup is included in the base price.

Your choice. Once it's tested and running in your environment, you're handed the keys and in charge. From there you can add a maintenance contract (covers ongoing support) or staff training (so your team can run it independently) — both separately priced, neither mandatory. Declining both is a legitimate choice; it just means any future work goes through a new SOW.

Fixed-price for templated deployments, scoped during the discovery call based on your actual environment — not hourly billing for well-defined work. Custom or open-ended engagements are scoped and priced individually.

Typical templated deployments run 2-4 weeks from signed SOW to tested handoff, depending on scope. Discussed and locked in during the SOW conversation, not a one-size-fits-all promise.

Yes — I work inside your environment using scoped, time-boxed access. If your infrastructure is costly to run and you can't provide a sandbox/dev tenant, that cost gets scoped into the SOW rather than absorbed silently — we'll cover this explicitly during discovery.

My own access to your environment follows the same Zero Trust principles I build for you — scoped to only what the engagement needs, time-boxed, logged, and revoked at handoff. Not just a policy — it's proof by example.

SOC2, PCI-DSS, HIPAA, and NIST 800-207 (Zero Trust Architecture) are the frameworks most of these patterns are already mapped against — relevant compliance requirements get confirmed and built into the SOW scope for your specific engagement.

Likely yes. The templates are proof-of-capability, not a limit on what I build. If you have a specific security/identity/AI-governance problem that isn't represented here, reach out and we can scope it as a custom engagement.

Both — remote is the default delivery model, but on-site engagements are available where it makes sense. Worth raising during discovery if it's a requirement.

Just me — PhalanxAI Security LLC is a single-member firm. Every engagement is delivered personally, not handed off to a bench of junior contractors. Capacity is managed by taking on engagements deliberately rather than overcommitting.