Skip to content

JWS Platform

Security Baseline

The floor every deployment starts from

  • Security-conscious teams
  • Client-handling agencies
  • Anyone storing user data

The problem

Security add-ons sold per feature mean most small apps run with none of them. The cheapest app deserves the same floor as the biggest.

How JWS solves it

Isolation, encrypted secrets, least-privilege access and audit trails — applied to every JWS deployment by default, not as an upgrade.

What you get

Tenant isolation

Row-level security separates every workspace's data.

Encrypted secrets

Env values and 2FA secrets are encrypted at rest.

RBAC everywhere

Roles and permissions on every organization action.

Audit logging

Security-relevant events recorded and reviewable.

How it works

  1. 1

    Deploy anything

    The baseline applies automatically.

  2. 2

    Configure access

    Roles, 2FA and sessions in settings.

  3. 3

    Review audits

    See who did what, when.

Security & privacy

This page describes the baseline itself: import analysis never executes code, secrets are write-only, sessions are revocable per device.

Cost impact

The baseline is included in every plan — security is not a pricing tier.

Honest limitations

  • Some advanced options are staged rollouts — status is shown honestly.
  • Complex stacks may need a manual review step.
  • Your application code quality remains your responsibility.

FAQ

Do I need DevOps experience?

No — the workflow is built for builders, not operators.

Can I leave later?

Yes — the Deployment Passport keeps your app portable.

What does it cost?

Estimates in EUR are shown before any provisioning.