Environment variable management
Replace shared .env files with controlled runtime access.
Local environment files are convenient until a team has multiple services, environments, contractors, and production credentials. Shortspan keeps related values in named secret groups and lets authorized developers run commands with those values from the CLI.
Why teams change
The .env file is a format, not an access-control system.
A copied environment file has no built-in owner, expiry, approval, or audit trail. Once sent, it can outlive the project, the developer account, and the credential it was meant to configure.
Shortspan keeps environment values behind workspace and project permissions. Teams can model a group such as Development or Staging, update its members centrally, and use it with the command that needs it. That reduces manual synchronization while preserving the familiar environment-variable interface applications already expect.
What Shortspan adds
Control around the workflow, not another workflow beside it.
Named secret groups
Bundle the values a service or environment needs, so developers select a meaningful group instead of assembling variables one at a time.
Process-level injection
Start a local server, migration, test suite, or script with approved values supplied to that process at runtime.
Central updates
Create a new encrypted version when values change and keep team members aligned on the current project configuration.
The workflow
From registered resource to accountable use.
- 01
Create the project boundary
Separate services and environments into the workspace structure your team already recognizes.
- 02
Build a reusable group
Add database URLs, service tokens, API keys, and other required values to a named group.
- 03
Run without copying
Invoke the application through the CLI and inject the approved group into its environment.
Operational outcomes
Make the secure path the understandable path.
- Less plaintext configuration stored on laptops
- Faster onboarding for developers joining an existing project
- Consistent names for shared development and staging environments
- Versioned updates instead of sending replacement files
Common questions
Know where the boundary is.
- Do applications need a Shortspan SDK?
- Not for environment injection. The CLI starts the child command with approved variables in its environment, so applications can continue reading ordinary environment variables.
- Can I keep different groups for development and production?
- Yes. Groups live within project boundaries and can represent the environments or workloads your team operates. Access can then follow the role and project membership appropriate to each boundary.
- Does this prevent every possible local copy?
- No tool can prevent an authorized process or user from deliberately copying data it can read. Shortspan reduces routine copying, separates use from management where configured, and records relevant access activity.
Read the implementation details
Documentation for this workflow
Related solutions
Connect the next part of the workflow
Start with one project and one access problem.
Create a workspace free, or tell us what your team needs to broker, approve, and review.