Skip to content

Under construction. Where it stands

Two ways to run it, once it’s out

Neither exists yet. The software will be free under AGPL-3.0. No hosted price has been set, so none is written here.

On your own servers

For a team that can look after a Node app and a database. It’ll be the way to keep everything under your own roof.

You’d install
A Next.js app and Postgres, on Vercel or anywhere that runs Node.
You’d connect
Your own Google OAuth client for Search Console, and your Bing Webmaster Tools access.
You’d look after
Updates, backups and the daily jobs that keep the history going.
You’d pay
Your host and your database, at their own prices. Nothing to Owlseen.
See what’s planned for self-hosting

At app.owlseen.com

The instance we’ll run, for those who’d rather not. It doesn’t exist yet.

We’d run
The app and its database, on servers in the EU, in Frankfurt (fra1).
You’d connect
Your workspace’s own Google OAuth client and your Bing access, on the Connections page.
Accounts
None yet.
Price
Not set.
Ask to hear when it’s ready

What running it would cost you

Owlseen has no line on this list. These are other companies’ services at their own prices, and someone’s time: check them for your volume when the time comes.

Hosting

Anything that runs Node, with scheduled jobs once a day.

Postgres

Everything it keeps lives here, including the daily copy of your figures, which grows with the number of sites and the time you run it.

Google and Bing

Search Console’s and Bing Webmaster Tools’ APIs are how the figures arrive, with your own accounts and within their limits.

Someone’s time

Updates, backups and an eye on the daily jobs. It’s the line people forget, so count it honestly.

Questions about running it

Is there a hosted plan?

Not yet. app.owlseen.com doesn’t exist yet and no price has been set. When there is one, this page will say so.

Can I try it on my machine?

Not yet. The code goes public with the first release, along with its install guide.

What’s the catch with my own Google OAuth client?

A client whose consent screen is still in Testing gets refresh tokens that expire after 7 days, so daily jobs would stop every week. It has to be published to production.

Will I be able to leave?

If you run it yourself, everything will be in your own Postgres database, and it’s yours.