Portable OAuth identity
The creator connects through official AT Protocol OAuth and the returned DID remains the trusted mapping boundary.
Official AT Protocol integration
Bluesky publishing built on portable, owner-held identity.
Novas uses official AT Protocol OAuth to connect the creator’s Bluesky profile, publish supported text and media, and retain the record evidence returned by the creator’s PDS.
What the connection is for
A narrow purpose for every provider permission.
Record-based publishing
Supported text, image, carousel, and MP4 workflows retain the official record URI and content identifier.
Public performance signals
Profile and post observations are synced on a bounded cadence with their original capture time.
Permissions and formats
Only what the product needs. Nothing hidden in the background.
atproto
transition:generic
Supported product formats
Text-only publishingSingle imageCarouselShort-form video
Safeguards that stay visible
- The connected DID, handle, and PDS identity are resolved from trusted OAuth data.
- Posts and blobs are treated as public federated records.
- Remote deletion is separately confirmed and does not claim to erase independent caches.
- Publishing and sync calls remain owner-scoped and bounded.
Signed OAuth, isolated ownership
OAuth sessions and signing material stay on the server, while every stored connection, publication, and metric snapshot remains scoped to the authenticated Firebase UID.
Federation stays visible
Novas records the official AT Protocol reference for creates and deletes. It also explains that independent relays, indexes, caches, archives, or recipients may retain copies.
Your content stays yours.
Create a verified account, then connect only the profiles you own and choose to manage with Novas.