Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.edgespark.dev/llms.txt

Use this file to discover all available pages before exploring further.

New EdgeSpark projects currently start with one default environment: production. That means your project has one live URL, one current database state, one current storage state, one current var set, one current secret set, and one deployment history for the environment you deploy to today.

​
Current environment model

Current default environment
URLproject.edgespark.app
Deploy withedgespark deploy
DatabaseCurrent project database state
StorageCurrent bucket contents
SecretsCurrent secret store
VarsCurrent plain env vars
PurposeYour live project environment today

​
Staging is coming soon

Staging support is planned but not publicly available yet. When it launches, staging and production will be isolated from each other with separate data, storage, vars, secrets, and deploy history. Until then:
  • edgespark deploy updates the current default project environment
  • there is no public staging URL yet
  • there is no public promote workflow yet

​
Check the current environment at runtime

The runtime exposes ctx.environment:
server/src/index.ts
import { ctx } from "edgespark";
import { Hono } from "hono";

const app = new Hono().get("/api/public/runtime", (c) => {
  return c.json({
    environment: ctx.environment,
  });
});

export default app;
For publicly created projects today, you should treat the default deployed environment as production.

​
See also

Deploy your project

The current public deploy flow with edgespark deploy, plus what is coming next for staging.

Manage secrets

How current environment-scoped secrets work today and what will matter once staging arrives.
Last modified on April 7, 2026