Multi-brand separation
Each brand, provider identity, destination, calendar and receipt is kept distinct.
Headless social publishing operations
Orbit is a cloud-hosted publishing controller for account owners and authorised teams. It keeps planning separate from provider actions, binds each approved media file and caption to one exact destination and time, and records provider-native evidence.
Capabilities
Each brand, provider identity, destination, calendar and receipt is kept distinct.
Approved media, destination-specific copy, account and UTC delivery time are bound to one immutable execution identity.
Media remains in an authorised Google Drive folder and is admitted only after exact checksum, size, type and folder verification.
Orbit uses provider OAuth and official APIs. A provider route remains disabled until its permissions, review and live certification are complete.
Provider acknowledgement, schedule and public delivery are separate states supported by immutable receipt hashes and native readback.
OAuth credentials are encrypted in the hosted vault and are not exposed to the public site, optional interface or project files.
TikTok integration
Product information
No. The direct-post integration is implemented for review, but it remains disabled until TikTok grants production access and an authorised live certification is completed.
No. TikTok access uses TikTok's authorisation screen, and a provider action also requires an exact approved release transaction inside Orbit.
No. Orbit is an independent social-media management service. TikTok is a third-party service connected only when an account owner chooses to authorise it.
Yes. The account owner can revoke Orbit through TikTok's account settings and can request deletion of the hosted Orbit credential and applicable account data through Support.