Plan & Packages
Package Management
View and monitor your active packages
Packages contain the resources allocated to your organization based on your plan.
What Are Packages?
Each package contains:
Sandbox Hours
- 1 Sandbox Hour = 1 hour of runtime for a single sandbox
- Consumed based on actual runtime
- Tracked per organization
Agent Credits
- Used for AI agent operations
- Computer use operations via MCP
- AI model inference calls
- Tool executions
Viewing Packages in Dashboard
Navigate to "Plan & Packages" in your organization:
You'll see a table of all active packages showing:
- Package ID
- Sandbox hours available
- Agent credits available
- Validity period (from/to dates)
- Priority level
- Grant date
How Packages Work
Package Grants
Packages are granted when:
- You purchase a plan
- Your subscription renews
- You purchase one-time resources
Package Priority
Packages have priority levels:
- Higher priority packages are consumed first
- Helps optimize resource usage
- Prevents waste from expiration
Validity Period
Each package has:
- Start date: When it becomes available
- End date: When it expires
- Expired packages are removed automatically
Monitoring Usage
Current Balance
In the Dashboard, view:
- Total sandbox hours across all packages
- Total agent credits across all packages
- Package details in the table
Usage Tracking
Monitor your consumption:
- Sandbox hours decrease as sandboxes run
- Agent credits decrease with AI operations
- Multiple packages are consumed based on priority
Package Lifecycle
Subscription Plans
For monthly subscriptions:
- New packages granted before billing cycle
- Ensures uninterrupted service
- Previous cycle packages may still be active if not expired
One-Time Plans
For one-time purchases:
- Package granted immediately after payment
- Valid for specified duration
- Expires after validity period
Managing Resources
Running Low on Resources
When resources run low:
- Monitor package table regularly
- Check expiration dates
- Purchase additional resources if needed
Optimization Tips
Maximize your packages:
- Stop Unused Sandboxes: Don't leave sandboxes idle
- Monitor Expiration: Use resources before they expire
- Choose Right Shapes: Use appropriate sandbox sizes
- Set Timeouts: Configure auto-stop for sandboxes
Example: Sandbox with Auto-Stop
import { LybicClient } from '@lybic/core'
const lybic = new LybicClient({
baseUrl: 'https://your-base-url.example',
orgId: 'ORG-your_id_here',
apiKey: 'lysk-your-api-key-here',
})
// Create sandbox with 2-hour limit
const sandbox = await lybic.createSandbox({
name: 'Auto-Stop Sandbox',
maxLifeSeconds: 2 * 60 * 60, // 2 hours
shape: 'beijing-2c-4g-cpu',
})Understanding Package Data
Package Table Columns
- ID: Unique package identifier
- Sandbox Hours: Available sandbox runtime
- Agent Credits: Available AI operation credits
- Not Before: Package start date
- Not After: Package expiration date
- Priority: Consumption priority (higher first)
- Granted At: When package was added
Package Status
- Active: Within validity period, available for use
- Expired: Past expiration date, removed from view
- Pending: Before start date (rare)