Skip to main content

Core Concepts

Influgen feels simple when the core objects are clear. This page covers the five concepts you will use everywhere in the product.

Characters​

A character is the main unit of work in Influgen. It combines identity, visual references, voice, settings, and performance history into one reusable profile.

A character typically includes:

  • Name and niche
  • Appearance and identity metadata
  • Personality and content style instructions
  • Reference image URLs
  • Optional LoRA model URL
  • Optional voice clone
  • Social accounts and platform-specific settings
  • Autopilot and publishing preferences

Think of a character as a compact operating system for content. The content engine reads from it, engagement systems reply in its voice, and analytics aggregate around it.

Content Engine​

The content engine is the layer that turns structured character data into publishable assets. It can create:

  • Single-image posts
  • Carousels
  • Captions and hashtag sets
  • Reels and short-form video
  • Talking head clips
  • Motion-transfer outputs
  • Weekly calendar batches

Instead of treating generation as a one-shot request, the engine pushes items through a state machine:

  • queued
  • generating
  • ready
  • approved
  • rejected
  • published
  • failed

This is why Influgen works well for teams: operators can inspect and approve outputs before they touch a live channel.

Publishing​

Publishing is separate from generation. A content item can exist without being scheduled, and a scheduled post can fail independently from the generation that created it.

Publishing in Influgen covers:

  • Platform connection state
  • Content adaptation per destination
  • Scheduled post records
  • Publish-now actions
  • Error codes like token_expired or rate_limited

Keeping publishing separate makes it easier to reroute the same approved asset across multiple channels.

Credits​

Credits are the usage currency inside Influgen. Actions that consume model or infrastructure resources deduct credits from the workspace balance.

Credits are used for operations like:

  • Image generation
  • Video generation
  • Motion transfer
  • Talking head jobs
  • LoRA training

Some examples from the current product:

  • New accounts start with 50 credits
  • Motion transfer defaults to 200 credits per 5 seconds
  • Custom LoRA training defaults to 500 credits

Plans include monthly credits, and credit packs let you top up without changing plan tier.

Autopilot​

Autopilot is Influgen's policy-driven automation layer. It is not "publish everything automatically." It is a set of rules that decides how much of the workflow should run without manual intervention.

Autopilot can influence:

  • Whether content is batch-generated on a schedule
  • Whether approvals are required before publishing
  • What platforms are targeted
  • How aggressively engagement systems reply

The best way to think about autopilot is controlled delegation. You define the character and the rules, then Influgen handles the repetitive work inside those boundaries.

How the concepts connect​

The normal lifecycle looks like this:

  1. Create a character.
  2. Generate content through the content engine.
  3. Spend credits as assets are produced.
  4. Approve and publish content to connected platforms.
  5. Let autopilot handle repeatable parts of the cycle.

If you understand those five objects, the rest of the product becomes predictable.