Modal integration. Find failing Modal functions from their logs, deploys and spend.
Praxen Inc. maps your Modal apps and functions, reads their logs, deployments and spend to find what broke or got expensive, and writes the fix in your code.
Get started for freeHow to set up Modal
The guide provides no measured total setup time. Both token fields must pass validation before discovery starts.
- Open Modal Settings → Tokens and create a token for the workspace you want to connect.
- Copy both the ak- token ID and as- token secret. Paste both into Modal’s connection form in Praxen Inc.
- Validate and connect. One token resolves to one Modal workspace; repeat with a different token for another workspace.
Permissions and access
Modal has no read-only token option: the token inherits its creator’s account permissions. Praxen Inc.’s sync only reads Modal. There is no read-only/full-access choice in the connection form, and secret values are not exposed by Modal; only names are mapped.
Discovery, refresh and the connected view
Inventory refreshes every 15 minutes. Environments contain apps, functions and endpoints, running sandboxes, volumes, secrets, queues and dicts. Functions are discovered through deployed apps; finished sandboxes are skipped. App pages carry stderr-line and metered-spend charts. Stderr counts are lines, not failures, and logs are retained by Modal for 24 hours. Spend is attributed per app and the newest unfinished hour can read low.
Disconnect and revoke access
Disconnect the Modal account in Praxen Inc., then revoke the token in Modal Settings → Tokens. A manual Sync refreshes inventory sooner than the next scheduled pass while connected.
Provider credentials and Praxen Inc.’s access mode are separate. Where write-capable tools exist, the connected account’s Settings page offers a Read-only switch. Turning it off permits writes subject to review and confirmation, but cannot add permissions to the provider credential. Agent-connected Kubernetes clusters stay read-only.
In the graph.
Every Modal resource Praxen Inc. picks up sits in the graph with its connections, config and history.
Environment App Function Class Sandbox Image Volume Secret Queue Dict Modal tools.
The calls Praxen Inc. can make to Modal when it looks into an issue.
Modal -
modalGetLogsGet Modal app logs: per-bucket volume by stream plus sampled lines -
modalListSandboxesList Modal sandboxes in an environment, with their state and resource shape -
modalListDeploymentsList Modal app deployments: version, who deployed, and when -
modalDescribeAppDescribe one Modal app: state, deploy provenance, and the functions inside it -
modalGetCostGet metered Modal spend, for one app or broken down across the workspace
Common questions.
How does Praxen Inc. connect to my Modal workspace?
Open Modal Settings → Tokens and create a token for the workspace you want to connect. Copy both the ak- token ID and as- token secret. Paste both into Modal’s connection form in Praxen Inc. Validate and connect. One token resolves to one Modal workspace; repeat with a different token for another workspace.
What Modal resources does Praxen Inc. sync?
Inventory refreshes every 15 minutes. Environments contain apps, functions and endpoints, running sandboxes, volumes, secrets, queues and dicts. Functions are discovered through deployed apps; finished sandboxes are skipped. App pages carry stderr-line and metered-spend charts. Stderr counts are lines, not failures, and logs are retained by Modal for 24 hours. Spend is attributed per app and the newest unfinished hour can read low.