Skip to main content

Overview

Genie Helper offers four pricing tiers designed to scale from individual creators to professional studios. Each tier has specific usage limits based on server resource costs and operational overhead.

Pricing Structure

Cost Basis

  • Server: $100/mo fixed (IONOS dedicated, self-hosted)
  • LLM inference: CPU-bound Qwen2.5 7B ~2-5s/call, ~4.8GB RAM pinned
  • Stagehand sessions: ~300MB RAM/active browser session → ~33 concurrent sessions ceiling
  • FFmpeg clip generation: ~30s CPU per clip (primary bottleneck)
  • Watermark operations: ~100ms (Sharp/ImageMagick, effectively zero cost)
  • Platform universe: 9 total platforms supported

Tier Limits Comparison

-1 indicates unlimited usage

Starter (Free)

Ideal for testing the platform with minimal resource commitment.

Creator ($49/mo)

Built for individual creators managing multiple platforms daily.

Pro ($149/mo)

Power users with high publishing volume across multiple platforms.

Studio ($499/mo)

Full-featured tier for teams and agencies managing multiple creators.

Usage Limits JSON Schema

This configuration is stored in Directus and enforced server-side:

Important Implementation Notes

Review these carefully before implementing tier enforcement

1. Thumbnail Operations on Starter

thumbnail_ops on Starter is 0, not -1. Thumbnails require video frame extraction. Since video is blocked on Starter (CSAM risk + cost), thumbnails must also be blocked. Wrong: "thumbnail_ops": -1 (accidentally enables video processing) Correct: "thumbnail_ops": 0 (properly blocks video operations)

2. Posts Published Counting

The current implementation treats one publish event = one content piece regardless of how many platforms it’s pushed to simultaneously. Example:
  • User schedules 1 post to 3 platforms simultaneously = 1 count
  • User schedules 3 separate posts to 1 platform = 3 counts
If you count per-platform-delivery instead, Creator at 90 posts becomes restrictive (3 platforms × 30 posts = only 30 pieces of content).
Document your counting convention clearly to avoid support tickets

3. Team Seats on Studio

Studio tier includes 5 team seats. You need a per-seat cost model for additional seats, or subscribers will onboard entire teams. Recommended overage pricing:
  • Additional seats: +$25/seat/month
  • Or: Hard cap at 5 seats, require custom enterprise pricing

Usage Tracking

Usage is tracked in the user_personas collection and enforced by:
  • API endpoint: server/endpoints/api/usage.js
  • Enforcement: Each operation checks current usage vs. tier limits
  • Reset period: Monthly, on billing anniversary
  • Storage: user_personas.usage_current_period JSON field

Usage API Example

Upgrade Flow

  1. User initiates upgrade: From pricing page or usage limit warning
  2. Payment processing: Payment gateway integration required
  3. Tier update: PATCH user_personas.pricing_tier
  4. Usage reset: Clear current period counters
  5. Immediate access: New limits take effect instantly

Downgrade Considerations

  • Graceful degradation: Existing scheduled posts remain in queue
  • Connection preservation: Platform connections stay active, new ones blocked
  • Data retention: All media and history preserved
  • Immediate enforcement: New limits apply at start of next billing period
  • Usage tracking: server/endpoints/api/usage.js
  • Tier enforcement: Applied in genieChat.js, queue.js, credentials.js
  • Frontend pricing: dashboard/src/pages/Pricing/index.jsx
  • User personas: Directus user_personas collection stores current tier