Skip to SEVA content
SparkGlimSEVA
Request consultation
Pre-release

Assessment only. Not yet suitable for any live election. Deployment and operation require authorized SparkGlim Security and Technical Teams.

Pre-release · source-reviewed design

Security includes the room.

Evaluate SEVA’s device, operator, transport and recovery boundaries before planning a supervised election environment.

A cryptographic design depends on real people, devices and procedures. SEVA’s operational controls need deployment-specific configuration and demonstrated tests, not assumptions carried over from source code or a marketing page.

Identify and restrict devices

Native gateway components require a client certificate, derive an operational surface from it and apply an allowlist. A separate restricted kiosk capability set limits local application features. Certificate enrollment, revocation, host lockdown and physical supervision still need validation on the actual deployment hardware.

Verify people and their authority

The source includes operator authentication and session components, while the current Master also has a separate local authenticator path. Complete passkey persistence and trustee-approval integration remain unfinished. A successful screen login must never be presented as proof of every server-side election permission.

Protect keys and software releases

Ed25519 release checks, software signing, a PKCS#11 signer and signing-key rotation tools exist in source. The inspected Center wiring uses software signing, so hardware-backed custody is not a deployment guarantee. Agree custodians, recovery, release trust and key destruction before stronger operational claims.

Rehearse failure and reconciliation

Plan supervised paper reconciliation, device loss, interruption, pause/resume and recovery rehearsals. Restricted backup and lifecycle-aware network components exist, but actual egress isolation, restore drills and physical media enforcement have not been established by this source review. Independent acceptance must include people and procedures as well as software.

Continue exploring

Local operation needs a complete plan.

SEVA is designed around locally hosted, in-person, supervised operations. This design direction does not establish a completed deployment.

Prepare the environment, not just the software.

Review governance, equipment, accessibility and evidence requirements with the responsible SparkGlim teams. Preparation does not approve live use.

Separate identity from the ballot.

Review SEVA’s intended identity and ballot separation, blind eligibility credentials, retention considerations and privacy limitations.

Readiness is evidence, not a date.

A clear distinction between SEVA source-reviewed components, integration and testing gaps, and future work without promised release dates.

Begin a requirements conversation.

Tell SparkGlim about the institution and evaluation you are considering. This enquiry is not registration, authorization or approval for an election.

Request consultation

Scope before commitment

Assessment only. Not yet suitable for any live election. Deployment and operation require authorized SparkGlim Security and Technical Teams.

Request consultationSecurity

Country context guides the consultation. It does not establish jurisdictional approval, regulatory compliance or product availability.