Publishing video content across multiple social media platforms is, at its core, an infrastructure problem. You have one source file. You have four platforms with different encoding requirements, different API authentication flows, different token expiry windows, and different content specifications. You have scheduling requirements, storage requirements, and considerations around data residency.
Most tools built for this problem are designed for the Western market — hosted offshore, priced in dollars, with storage defaulting to servers outside India. Beam is built differently.
What Beam Is
Beam is a managed video publishing platform that takes one MP4 file and distributes it to YouTube, Instagram Reels, Facebook, and LinkedIn — simultaneously or on a scheduled queue. It is deployed on Bagful infrastructure. Every customer instance is isolated — separate subdomain, separate MySQL database, separate S3-compatible storage bucket. India-hosted by default.
The Content Ownership Problem
When a video is uploaded to Instagram, YouTube, or LinkedIn, the platform stores it on their infrastructure, re-encodes it to their specifications, and compresses it for their delivery network. What you uploaded is not what gets stored on their servers.
When you need that video back — for a re-edit, an archive, a compliance record, or simply because you want your own work — you discover that retrieving it cleanly requires third-party download tools, produces watermarked output, and returns a compressed version of the original file you created.
Beam solves this by separating storage from publishing. Every video uploaded through Beam is stored in your own S3-compatible bucket before it is distributed to any platform. Your original file stays in your infrastructure. Always.
Storage Options
- Cloudflare R2 — Customer provides their own R2 bucket. Zero egress fees. Global edge network. Customer retains full independent ownership.
- Bagful Object Storage — India-hosted. Data residency within India. Managed by Bagful. Suited for businesses with data localisation requirements.
AI-Optimised Publishing — Per Platform
Every platform has its own content logic. What works on LinkedIn does not work on Instagram. What ranks on YouTube does not land on Facebook. Beam's AI content optimisation layer handles this automatically.
Connect your own OpenAI API key. Write one title and one description — in your own words, in your own voice. Beam generates platform-optimised versions for each network before publishing.
- YouTube — keyword-rich title up to 100 characters, structured description, hashtags at bottom
- Instagram — punchy opening hook, casual tone, 3 to 5 hashtags, emoji where natural
- Facebook — conversational tone, comment and share oriented, no hashtag stuffing
- LinkedIn — professional and insight-led, hook in first line, maximum 3 hashtags
You review and approve every version before anything goes live. The AI assists. You decide.
Authentication Architecture
Beam uses OAuth 2.0 for platform authentication. Each platform has its own token management.
- YouTube — OAuth tokens are permanent. One-time setup.
- Instagram and LinkedIn — Access tokens expire every 60 days. Beam includes a reconnect flow that handles token renewal without disrupting scheduled publishing queues.
- Facebook — Page Access Token, connected through Meta's standard OAuth flow.
The 6-step in-app setup wizard walks through each platform connection. No API console access required for the end customer. Bagful manages the OAuth application credentials on the infrastructure side.
Scheduling Infrastructure
Beam's scheduling engine runs on a server-side cron processor that executes every minute. Scheduled posts are queued in the database with their target publish time and platform combination. The cron job picks up due posts, calls the publishing pipeline, handles retries on API failures, and updates the post status log. Customers can view and manage the scheduled queue — reschedule or delete before execution.
Technical Specifications
| Component | Specification |
|---|---|
| Platforms | YouTube, Instagram Reels, Facebook, LinkedIn |
| Language | PHP |
| Database | MySQL |
| Storage | S3-compatible — Cloudflare R2 or Bagful Object Storage |
| AI | OpenAI API — per-customer key, per-instance storage |
| Authentication | OAuth 2.0 — per platform |
| Scheduling | Server-side cron — 1-minute resolution |
| Deployment | Isolated managed instance per customer |
Deployment Model
Beam is deployed as a managed instance on Bagful's infrastructure. Each customer deployment is fully isolated — dedicated subdomain, dedicated MySQL database, dedicated storage bucket, dedicated OAuth application credentials per platform.
This architecture eliminates cross-customer data exposure and allows per-customer configuration without shared environment risk. Bagful manages server maintenance, security patching, uptime monitoring, and OAuth token infrastructure. The customer manages their content, their schedule, and their storage bucket credentials. No cPanel access. No file management. No server administration required.
Data Residency
For businesses with data localisation requirements — particularly relevant for Indian businesses handling customer data or operating under sector-specific compliance frameworks — Bagful Object Storage provides India-hosted storage with no cross-border data transfer for stored video files.
Publishing API calls to YouTube, Instagram, Facebook, and LinkedIn necessarily traverse those platforms' global infrastructure. The source file storage, however, remains within India-hosted Bagful infrastructure.
Pricing
| Plan | Price | Billed As | Notes |
|---|---|---|---|
| Monthly | ₹499/month | ₹499 every month | ₹1,000 one-time setup fee applies |
| Quarterly | ₹433/month effective | ₹1,299 every 3 months | No setup fee |
| Annual | ₹417/month effective | ₹4,999 per year | No setup fee. Best value. |
All features included across all plans. No per-platform charges. No storage overage charges within reasonable usage. Managed setup and onboarding support included. Existing Bagful customers can connect Bagful Object Storage directly.
Who Beam Is For
- Indian SMBs publishing video content regularly across platforms without a dedicated technical team
- Founders and business owners managing their own social presence
- Creators who want platform-optimised content without writing four separate versions
- Businesses with data residency preferences for stored content
- Any organisation that has recognised content ownership as an operational risk and wants to address it with minimal infrastructure overhead
Ready to get started? Visit fidus.one/apps/beam for details, or contact the Bagful team to discuss your setup.