Flux Energy
Royalty and settlement data deserve the same care as the rest of your financial systems. Flux Energy uses layered controls, verifiable audit trails, and identity-aware access. This page shows technical and procurement teams what is in place.
Security
Every building is a working security department. Click one to learn what it defends, or take the tour.
drag or swipe to pan · scroll or pinch to zoom · double-click to reset
2-minute interactive tour. Sound on.
Architecture
Enterprise deployments follow a cloud-native pattern: verified identity and policy at the edge and API, isolated tenant logic, managed data stores, and observable operations. This replaces “trust the castle wall” with verification at each tier, consistent with zero-trust design principles.
Compared to legacy DMZ-only designs: each layer performs its own job across edge transport, gateway policy, application authorization, and data integrity, so responsibility does not rest on a single perimeter device.
Controls
Principles below reflect shipped server and application behavior: identity, encryption, auditability, and partner-scoped payments.
JWT-based sessions, database-driven RBAC, bcrypt password hashing, optional TOTP-based MFA and WebAuthn passkeys for accounts that enable them, and per-tenant isolation mean access is decided on each request, not implied by network location alone. That is the operational core of a zero-trust posture for multi-tenant SaaS APIs.
HTTPS for all client and API traffic. Sensitive integration secrets use AES-256-GCM at rest. Payment card data remains in PCI-scoped processor environments. Flux Energy orchestrates initiation and status without hosting cardholder data on application servers.
Financial and settlement actions write to a hash-chained audit log so event sequences resist silent alteration, supporting royalty traceability and independent review.
Granular roles, server-validated sessions, optional IP controls, and request fingerprinting constrain abuse. Rate limits on authentication and sensitive routes reduce the blast radius of credential misuse.
Structured security logging, rate-limit events, and pattern-based intrusion signals support timely detection. Policies are enforced in production, not left as passive configuration.
Managed PostgreSQL supports automated snapshots and point-in-time recovery; operational runbooks cover restore procedures for continuity planning.
Documented controls map to SOC 2 trust-services criteria: least-privilege access, change-aware logging, and evidence that shows who did what and when. Session activity, administrative actions, and settlement runs leave an audit trail your security team can review without reconstructing spreadsheets. The mapping and supporting evidence aid diligence but are not a CPA attestation.
Double-entry friendly exports, period discipline, and reconciliation-oriented outputs help finance tie royalty recognition to the general ledger your auditors already test.
Every customer’s data is scoped to its own tenant boundary. Queries, APIs, and exports do not cross organizations by design. Isolation is enforced twice: once in application logic, and again inside PostgreSQL with row-level security policies that the application’s own runtime credentials cannot bypass. The isolation model is formally verified, not just tested.
SCADA and turbine telemetry are read through a lightweight collector deployed on your own network alongside the plant historian. It polls locally, buffers, and pushes readings outward over an authenticated, encrypted connection. Flux Energy does not open an inbound connection into plant equipment. You hold a local kill switch and a connection access log for every collector, so vendor access is determinable, disableable, and detectable.
Know Your Customer workflows help verify counterparties before funds move, supporting treasury policy and disbursement expectations.
ACH and card rails run through Plaid, Stripe Connect, and Modern Treasury. Bank credentials stay in their compliance boundaries; Flux Energy coordinates initiation and status with a smaller in-scope footprint for your assessments.
Documented information security policies, access-control rules, and data-retention schedules are reviewed on at least an annual cycle. Risks are identified through architecture review, dependency and vulnerability monitoring, and audit findings, then tracked with management accountability, not ad hoc heroics.
Automated dependency scanning in CI, a generated software bill of materials for every build, upstream update channels, and prioritized patch windows for critical and high-severity findings reduce exposure before it reaches production. Secrets stay out of source; changes ship through reviewed pipelines.
Compliance
Flux Energy maps product and operational controls to SOC 2 trust-services criteria for access, logging, change awareness, and evidence retention. This lets diligence move from questionnaire to substantiated artifacts. Flux Energy does not claim a Type I or Type II attestation; confirm current status during review.
The reference architecture is designed so large operators can map controls to enterprise security questionnaires without custom one-off engineering for every RFP. The same standards posture extends to accessibility: Flux Energy targets WCAG 2.1 AA. See our Accessibility Statement.
Contrast
Classic “inside means trusted” designs fail modern threats. Flux Energy assumes verification at each tier, not once at the firewall.
| Legacy pattern | Failure mode | Flux Energy |
|---|---|---|
| Single choke-point firewall | One misrule or compromised device exposes the interior. | Edge TLS, gateway policy, application auth, and data controls enforce independently. No single gate carries the whole burden. |
| Flat trusted intranet | Lateral movement after one foothold. | Tenant-scoped APIs and RBAC limit what any single credential or role can touch. |
| Static firewall tickets | Untracked drift and emergency holes. | Infrastructure-as-code and reviewed deploy pipelines change the surface predictably. |
| Minimal logging | No evidence for incident response or audit. | Security-oriented logging, rate-limit signals, and hash-chained financial audit entries. |
| Long-lived shared secrets | Stolen keys stay valid for months. | Server-validated JWT sessions, rotated application secrets, and scoped tokens for integrations. |
Rollout
We plan the rollout around your existing operations, with time for migration, testing, and a parallel run.
We’ll walk through the architecture, control evidence, and deployment posture under NDA. Send your security questionnaire or procurement timeline, and we’ll respond to the specifics.