CloudAEye for 
YouTube
Your team already recorded it. Now new developers can find it.
Your architecture walkthroughs and recorded demos already explain how things work. CodeCortex reads their captions alongside your code, so new developers get answers instead of a playlist.
Captions from your own channel You choose the videos
YouTube · example onboarding question
-
Every call between services carries a signed token.
-
The gateway mints it, and it lasts five minutes.
-
Services verify it with the shared middleware. They never call the auth service.
-
So the auth service isn't a single point of failure.
Indexed from the captions of a video you selected.
New
developerHow does a request get authenticated between services?
Tokens are minted in gateway/auth/tokens.py with a
five-minute expiry. Each service checks them in
common/middleware/verify_token.py instead of
calling the auth service.
-
When the provider has a blip, every client retries at once.
-
We added jitter, so retries spread out instead of landing together.
-
It's in the retry helper, capped at three attempts.
-
Before that, our retries made outages worse.
Indexed from the captions of a video you selected.
New
developerWhy does the payment service add jitter to retries?
Retries without jitter piled onto the provider during outages.
retry_with_backoff() in
payments/retry.py adds random jitter and caps
attempts at three.
-
Now let's run a refund through the whole system.
-
Create a test payment with a seeded card, then call the refund endpoint.
-
Watch the worker logs. You'll see the provider stub respond.
-
That's the full path: API, worker, then ledger.
Indexed from the captions of a video you selected.
New
developerHow do I test a refund end to end?
The demo follows a refund from the API to the worker to the
ledger. Seeded cards come from scripts/seed.py, and
the endpoint is POST /payments/:id/refunds in
api/refunds.py.
Accurate answer from the team's knowledge.
Google Drive
OneDriveConnect once.
Every new hire benefits.
Set it up once in the CloudAEye console. After that, new developers just ask.
-
Week one:
get oriented.Learn the services, the setup, and the architecture from the talks your team already recorded, without waiting for someone to walk you through it.
First-week questions -
First change:
know the why.Before touching unfamiliar code, find the walkthrough or deep dive that shaped it.
First-change questions -
Every hire after:
answer once.Point new teammates to CodeCortex. The talk you gave once keeps answering.
Ongoing questions
You choose
what gets indexed.
Select videos from your channel's uploads. Only their captions are indexed, in timestamped segments of about 30 seconds.
61 minutes of captions in 3 videos will be indexed.
CodeCortex indexes
- Caption tracks of the videos you select
- One track per video, English when available
- Segments of about 30 seconds, each with its timestamp
Answers from talks
you already gave.
Recorded walkthroughs hold the reasoning nobody wrote down. A new developer shouldn't have to scrub through an hour of video to find it.
Learn the architecture from a walkthroughFirst week
Get the explanation from a recorded architecture talk alongside the code it describes.
How do services authenticate each other?
What does the gateway do?
Follow a recorded setup demoFirst week
Find the step you need in a demo without rewatching all of it, with the scripts and endpoints it uses.
How do I test a refund end to end?
Find the reasoning behind a designFirst change
Recover why something was built a certain way, as the person who built it explained it.
Why does the payment service add jitter to retries?
Catch up on a deep dive you missedFirst change
Ask about a recorded deep dive on the service you're about to change.
How does the ledger handle partial refunds?
Make recorded talks findableOngoing
Turn a channel of walkthroughs into answers. Questions reach the right talk without anyone remembering which one it was.
Which talk explains the event pipeline?
Stop answering the same question twiceOngoing
Link the question to the talk instead of re-explaining it. Every later hire hears the same version.
Which talk covers the architecture?
Is there a recording of the payments overview?
Your next new hire.
A faster first week.
Onboard developers in days, not months. Create a CloudAEye account, connect YouTube, and choose the videos a new developer should watch.
Connect YouTube Talk to our team-
1
Sign in to CloudAEye
Create an account or sign in to the CloudAEye console.
-
2
Connect YouTube
Sign in with Google and approve YouTube access for your channel.
-
3
Choose videos, then ask
Select videos that have captions. When indexing finishes, ask it the questions a new developer would.
A few things worth knowing.
What access does CloudAEye request?
Google's consent screen lists two YouTube permissions: view your
YouTube account (youtube.readonly), and see, edit,
and delete your videos, ratings, comments, and captions
(youtube.force-ssl). YouTube only allows caption
downloads through the second one. CloudAEye uses them to list your
uploads, read video titles, and download captions. It never
changes anything on your channel.
What if a video has no captions?
It can't be indexed. Add captions in YouTube Studio, then select the video.
Does connecting YouTube also ask for Google Drive?
No. Google Drive and YouTube are connected separately, and each asks only for its own permissions.
Can I remove a video after it's indexed?
Yes. Remove an indexed video and CloudAEye deletes its indexed captions.
What happens if I disconnect YouTube?
CloudAEye deletes the stored connection and the captions it indexed.