Home › Blog › 8,500 Kilometers to a Better Sky

← All articles

July 23, 2026  ·  🔭 Astronomy

8,500 Kilometers to a Better Sky – How I Bought My Remote Rig in Texas

The sky over Germany is, to put it kindly, not a revelation. Light pollution, clouds — and honestly, I'm not a night owl willing to stay up into the early morning hours for the few clear nights we get. At some point I stopped fighting it and started looking for a different sky instead — 8,000 kilometers away, under Bortle 1, far out in rural Rockwood near Brady, Texas.

The seven-hour time difference that comes with it is not a drawback but rather a gift: when it's night there, it's mid-morning here. I can watch the stars come out over Texas live — well-rested, in daylight, coffee in hand — instead of pushing through until deep into the night and nearly collapsing at the telescope from fatigue.

This is the story of how I got there.

Why Used, and Why Remote

Remote astrophotography sounds elaborate and exclusive, but at its core it's a thoroughly pragmatic solution to a simple problem: instead of hauling your telescope to where the sky is good, you install it there permanently — and operate it from your desk at home. Providers like Starfront Observatories rent out hosting spots for exactly this — a pier under a roll-off roof, power, internet, and someone on site who checks on things in an emergency.

Building a complete rig from scratch, however, quickly runs into five figures. So I looked for a used one that was already on site — someone leaving the hobby or rebuilding their setup.

A Tuesday Evening on the Sofa

Starfront runs a dedicated channel on its Discord server where members sell used equipment — up to complete “turnkey rigs”, ready-to-run systems you take over together with the hosting spot. I watched the prices there for weeks. Complete systems typically ranged between $5,000 and $15,000 — solid, but beyond what I wanted to spend.

Then, on a Tuesday evening, on the sofa in front of the TV, an offer appeared in the channel: a turnkey rig for $4,200. No photo, just a list — but what a list:

All fully assembled on a pier in Building 8.

I thought about it briefly — and quickly researched what all these parts would cost new in the US. The sum of the list prices was considerably higher, roughly double or more. Then I wrote to the seller: I want to buy, what do I need to do? And that's how it started.

We quickly agreed on payment via PayPal. And so, still from the sofa, I transferred $4,200 straight to the USA. My wife, half watching, asked what any sensible person would ask in that moment: “Are you sure this isn't a fake?” My honest answer was: “Hmm. I hope not.”

It wasn't a fake. Everything went fine.

A small but effective protection against fake offers is built into the community itself: you can recognize a genuine Starfront customer by the Discord tag “Starfront Customer”. Anyone carrying that role tag is verified by the operator as a paying user — not one hundred percent proof, but a first hurdle that pure scammers probably wouldn't clear.

Starfront's marketplace rules also specify exactly how such a handover should work — the transfer of ownership and of the hosting spot. We followed them to the letter: both sides opened a ticket with Starfront, including the purchase agreement and payment receipts, and from there it proceeded step by step and surprisingly quickly. The operator acting as a neutral third party takes much of the risk out of such a transaction — you're not relying solely on the word of a stranger on the internet.

In fact, the team behind it is what convinced me most in hindsight. Starfront currently employs around 15 people, and everything runs through a ticket system: inquiries, work orders, small hands-on jobs at the rig. Whatever I submit there is handled surprisingly fast, done well, and with genuine friendliness. One example: for the handover of the hosting spot I had ordered a new pier camera, a ZWO ASI662, which initially wasn't aligned well. One ticket — and by the next day everything was fixed, including the questions about the Pegasus ports I still had anyway.

The rig was ready to operate, they said. The word “ready to operate” is the core of this story.

You Don't Buy a Telescope, You Inherit a System

Taking over a used rig feels great at first: it runs, it has already produced images, there's nothing to assemble. What nobody tells you: you inherit not just the hardware, but also the previous owner's configuration, cables, accounts, and assumptions.

The computer still logged in with the previous owner's Windows account. The software's error messages went to his email address — and to a Discord webhook I didn't even know about. The smart power strip used to switch power remotely was still tied to his cloud account — meaning he could theoretically have switched off my mount, the computer, and the Pegasus electronics from his phone, anytime, from anywhere. Not out of malice, but because nobody had thought to re-register it.

So the first realization was uncomfortable: before photographing a single star, I had to make the whole system mine. Accounts, certificates, passwords, access. That's invisible work and absolutely necessary — but honestly, I even enjoyed it. Nothing brings you closer to your own system than taking it over piece by piece and really getting to know it in the process.

The Detective Work

The real effort, however, was elsewhere. When your telescope is 8,000 kilometers away and something jams at three in the morning, you can't just walk over and take a look. You need complete documentation of your own setup — which cable is plugged into which port, what happens when you switch off a port remotely, which switch resets which device.

So I started documenting. And discovered that almost everything I initially assumed about my own setup was wrong in some detail.

The best example: the USB cabling. For the handover, the previous owner and I had done a Teams session — he showed me the software, the workflows, the quirks of the setup via screen sharing. A genuinely helpful appointment, and one I would recommend to anyone. But no substitute for reality: from that session I adopted, among other things, the statement that my main camera was connected directly to the computer. That's how he remembered it, that's how he passed it on, that's how I wrote it down.

A readout tool then showed it was plugged into a completely different hub. I corrected the documentation — and was still wrong, because I had confused the hub's internal port numbers with the labels on the case. Only when a technician on site actually put his hands on the sockets did the mapping finally match. While he was at it, he took current photos of the rig for me — priceless when you otherwise never see your own setup with your own eyes.

Bringing Everything Up to Date

The system I took over was no longer fresh on the software side. You know the saying “never touch a running system” — and there's something to it. Still, I simply feel more comfortable when everything is up to date. Especially with a computer I can't reach with a USB stick in an emergency, I don't want to sit on half-outdated software.

So a whole round was due: pending Windows updates, numerous ZWO driver updates, new firmware for the AM5 mount, updates for the Pegasus electronics, plus software like ASTAP. None of it is spectacular, all of it is fiddly — and doing it remotely adds the extra thrill that a half-finished installation can wreck your remote access and lock you out.

An Eye on the Rig

One building block was still missing: good software for the pier camera — the small camera that doesn't photograph the sky, but watches my own rig and the patch of sky above it. It's my eye on site. Is the mount where it should be? Is the roof open? Are clouds rolling in?

Through tips in the Starfront Discord I found the tool I use today: PFR Sentinel. It turns the pier camera into a small control room — live view, overlaid status for weather, roof, and seeing, automatic timelapses of the night, an all-sky view, and even meteor detection.

For the notifications I've since set up my own Discord server. The status messages flow in automatically — including current images from the pier camera, so I can check on my rig and the sky above it anytime, from anywhere, without having to log in somewhere first.

This kind of concrete recommendation, by the way, is the real value of the community: you don't have to find every tool yourself — you inherit the experience of people who have already solved the same problem.

The One Morning (in Texas: Night 😉) That Made It All Worth It

After all the cleanup work came the part I actually do this for: the guiding.

The inherited guiding configuration was a quiet train wreck. Exposure times far too long for the fast harmonic-drive mount. A profile that had never been set up properly. The system worked — with a guiding error of about 1.1 arcseconds. Not bad, but not what you book a Bortle 1 sky for.

So I rebuilt it from the ground up — for me it was mid-morning, in Texas the middle of the night, and this is exactly where the time difference paid off again: I could immerse myself in PHD2 for three hours straight, without time pressure and without fatigue, instead of attempting it bleary-eyed at three in the morning. Exposure halved, recalibrated, a clean profile built, the settings reviewed one by one. The calibration's orthogonality error dropped from 6.4° to 0.3°. The guiding error from 1.1″ to 0.61″ — the best value this rig has ever shown.

I had a genuine helper at my side: Claude AI. I could simply drop in the PHD2 log files or even just screenshots of the guiding window — and Claude read the values, understood the relationships, and gave me not just concrete configuration suggestions but also explained them. Why exposure time is so critical on a harmonic-drive mount, what the orthogonality error means, what to look for when choosing guide stars. The fact that an AI can draw the right diagnosis from a blurry screenshot and then explain it to me in plain language genuinely amazed me.

And the most satisfying part: the improvement wasn't luck, it was predictable. There was a clear symptom — guiding was twice as bad in one axis as in the other — a diagnosis, and a change that fixed exactly that. That's the moment all the dry documentation work pays off: you don't just know it got better, you know why.

What I Would Advise

If you're toying with the idea of running a remote rig yourself, I'd recommend two routes.

The first: buy a used system already on site. The big advantage is that it's proven and set up — someone got it running, and it has already produced images under exactly this sky. That's precisely what I did.

The second: buy new, but directly in the US from a dealer that partners with Starfront. These dealers know from experience which combinations work best there — and US prices are considerably lower than ours anyway.

And a few things I learned along the way:

The purchase price is the starting point, not the final price. The hardware is one thing. The time to truly understand the system, take it over cleanly, and document it honestly is the other. That time is real — but, as I said, for me it wasn't a loss, it was half the fun.

Distrust the configuration, not the hardware. Telescopes, cameras, and mounts are usually impeccable. What bites you are settings, cables, and accounts that someone else set up according to their own ideas.

And the best part, to finish: in the first few days I learned more about my equipment than I ever would have with a straight new purchase — simply because I had to question every detail. The rig now stands in Texas, it guides cleanly, and if something jams at three in the morning, I know exactly where to look.

The sky over Germany is still not a revelation. But the one over Rockwood is — and from my desk, it's just one click away.

🔭 The complete setup in detail — hardware, software stack, power and network topology: My Rig @ Starfront in Texas