Banking · Controlled evaluation

Plexadi Enterprise Pilot

Evaluate lower-data transport under real-world network constraints.

SDK under development · Patent-pending technology · Pilot availability and scope subject to agreement

Download pilot brief · PDF, 1 page

One bank use case

Transfer non-sensitive test files between two isolated bank test environments over a bandwidth-constrained link. Compare the bank’s existing transfer method with the selected Plexadi approach using identical data and network conditions.

The question to answer

Can the selected approach reduce total network traffic while meeting the bank’s agreed integrity, fidelity and delivery requirements? Exact-file transport and semantic reconstruction are evaluated separately, not treated as equivalent.

No fixed savings, performance improvement, security strength or energy reduction is promised.

Bank pilot flow· Scope & mutual NDA agreed first
  1. 01

    Baseline testing

    Existing transfer method

  2. 02

    Plexadi evaluation

    Same data & link profiles

  3. 03

    Results review

    Pre-agreed criteria

  4. 04

    Licensing decision

    Only if criteria are met

Measure before deciding.

Network payload

Total bytes sent, including metadata, dependencies, receiver setup and retries. Compare first-time and repeat transfers.

End-to-end time

Time from transfer start to usable content at the receiver, including reconstruction; report median and tail latency.

Delivery reliability

Completed transfers, failures and retries under identical bandwidth, latency, packet-loss and interruption profiles.

Integrity & resources

For exact files: byte equality and checksum verification. For semantic reconstruction: separately agreed fidelity checks. Record receiver CPU, memory and storage; measure energy only with suitable instrumentation.

Before testing, jointly agree the dataset, baseline, network profiles, repetitions and numeric acceptance thresholds. Success means meeting those pre-agreed criteria, not a percentage chosen after the results. Include all resources and report unsuccessful runs.

A safe test boundary

  • Mutual NDA before detailed technical exchanges.
  • Synthetic or approved non-sensitive files only; no customer or production data.
  • Isolated endpoints, agreed access, retention and deletion arrangements; no production integration.
  • This transport pilot does not validate P7 cryptographic security or regulatory compliance. Those require separate independent reviews.

From pilot to licensing

  1. 01

    Agree scope & NDA

    Confirm readiness, test boundaries and acceptance criteria.

  2. 02

    Run & review

    Evaluate alongside the baseline and jointly review the complete results.

  3. 03

    Decide & license

    If criteria are met, agree integration, any further audits and SDK, enterprise-site or per-patent licensing terms.

Explore licensing

Request a pilot discussion

Tell us about your bank, test environment and evaluation goals. Scope, availability and terms are agreed individually under a mutual NDA. Do not include confidential, customer or production data.

Materials you want to discuss *

Your details are used only to respond to this request.

Book a pilot meeting

45 minutes on Google Meet · Monday–Friday, 08:00–17:00 Alicante time (Europe/Madrid).