# Database support in the future?

**URL:** <https://forum.storj.io/t/database-support-in-the-future/32026>\
**Category:** Developer Discussions\
**Created:** [July 16, 2026, 5:35pm UTC](https://forum.storj.io/t/database-support-in-the-future/32026 "2026-07-16T17:35:00Z")\
**Posts on this page:** 13\
**Page:** 2

<div class="post-metadata">

**Author:** ![michaln](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/michaln/32/62_2.png) [@michaln](https://forum.storj.io/u/michaln)\
**Post date:** [August 7, 2026, 6:47am UTC](https://forum.storj.io/t/database-support-in-the-future/32026/21 "2026-08-07T06:47:49Z")

</div>

btw, did you try to run satellite with crdb but using postgres implementation? I don’t remember how strict is crdb compatibility with PG but there is a chance it will work. It’ might be a bit less optimal (slower) in few places but shouldn’t be a problem for smaller satellte.

---

<div class="post-metadata">

**Author:** ![kocoten1992](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/kocoten1992/32/7819_2.png) [@kocoten1992](https://forum.storj.io/u/kocoten1992)\
**Post date:** [August 7, 2026, 5:58pm UTC](https://forum.storj.io/t/database-support-in-the-future/32026/22 "2026-08-07T17:58:13Z")

</div>

Good idea, let me try that on test infra, it will lower the cost for both of us, if thing break now I only need to fix that query and upstream it to you.

---

<div class="post-metadata">

**Author:** ![Toyoo](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/toyoo/32/1126_2.png) [@Toyoo](https://forum.storj.io/u/Toyoo)\
**Post date:** [October 1, 2026, 2:57am UTC](https://forum.storj.io/t/database-support-in-the-future/32026/23 "2026-10-01T02:57:09Z")

</div>

> [@Toyoo](#):
>
> It’s like vibecoding a new piecestore.

Lol, just tried out of curiosity. [Claude](https://claude.ai/share/6e2daac6-8b04-46a5-a7a1-5959ce8bfed5) , thought it would take a full session limit, but no. It only took just a couple of dollars in tokens. It’s… tempting 🤣

---

<div class="post-metadata">

**Author:** ![kocoten1992](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/kocoten1992/32/7819_2.png) [@kocoten1992](https://forum.storj.io/u/kocoten1992)\
**Post date:** [October 1, 2026, 3:12am UTC](https://forum.storj.io/t/database-support-in-the-future/32026/24 "2026-10-01T03:12:10Z")

</div>

You can throw in my repo too, ask it to look at commit related to postgres [GitHub - kocoten1992/patch\_sat: some patch for storj satellite · GitHub](https://github.com/kocoten1992/patch_sat)

I do use comby, but compiling it is annoying, so here the static binary build, could upload and ask it to use it too: [upbin — shared folder](https://upbin.cc/s/vPdsq6p)

P/s: wait, this isn’t about database, it about new storage on storagenode?

---

<div class="post-metadata">

**Author:** ![kocoten1992](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/kocoten1992/32/7819_2.png) [@kocoten1992](https://forum.storj.io/u/kocoten1992)\
**Post date:** [October 1, 2026, 3:22am UTC](https://forum.storj.io/t/database-support-in-the-future/32026/25 "2026-10-01T03:22:25Z")

</div>

Unrelated, I’m thinking about asking it to support WebRTC on storagenode and a uplink.js on browser side - to bypass gateway entirely, maybe it can get more adoption?

---

<div class="post-metadata">

**Author:** ![Alexey](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/alexey/32/41_2.png) [@Alexey](https://forum.storj.io/u/Alexey)\
**Post date:** [October 1, 2026, 3:42am UTC](https://forum.storj.io/t/database-support-in-the-future/32026/26 "2026-10-01T03:42:14Z")

</div>

Yes, it would be fantastic to create a version of uplink.js capable of running in the browser. In that case, a gateway would no longer be needed.  
Typically, uplink runs on the backend, which lowers the system’s overall security: you would have to transmit your access grants there, meaning client-side end-to-end encryption would no longer be an option.

---

<div class="post-metadata">

**Author:** ![kocoten1992](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/kocoten1992/32/7819_2.png) [@kocoten1992](https://forum.storj.io/u/kocoten1992)\
**Post date:** [October 1, 2026, 3:59am UTC](https://forum.storj.io/t/database-support-in-the-future/32026/27 "2026-10-01T03:59:08Z")

</div>

Ah, I explain my point poorly, it mean for consume content (download only) via short lived access grant that limit to download specific files.

But it true I’ve not investigate this path yet, so it might not be possible, I don’t know.

---

<div class="post-metadata">

**Author:** ![Toyoo](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/toyoo/32/1126_2.png) [@Toyoo](https://forum.storj.io/u/Toyoo)\
**Post date:** [October 1, 2026, 12:19pm UTC](https://forum.storj.io/t/database-support-in-the-future/32026/28 "2026-10-01T12:19:52Z")

</div>

> [@kocoten1992](#):
>
> P/s: wait, this isn’t about database, it about new storage on storagenode?

Yep!

> [@kocoten1992](#):
>
> Unrelated, I’m thinking about asking it to support WebRTC on storagenode and a uplink.js on browser side - to bypass gateway entirely, maybe it can get more adoption?

This might be relevant: [JS library for the browser - #7 by jtolio](https://forum.storj.io/t/js-library-for-the-browser/6537/7)

---

<div class="post-metadata">

**Author:** ![kocoten1992](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/kocoten1992/32/7819_2.png) [@kocoten1992](https://forum.storj.io/u/kocoten1992)\
**Post date:** [October 1, 2026, 12:29pm UTC](https://forum.storj.io/t/database-support-in-the-future/32026/29 "2026-10-01T12:29:06Z")

</div>

Thank you! They do think about it 😬 - but there might be a problem.

Some strict site will have CSP (content security policy), it only allow js to fetch some specific urls, storagenode are everywhere, it will run right into this wall. I think we must use supported P2P protocol, I did some research, a single webrtc data channel is ~300-400kb max (but not including data buffer yet), so we could spawn it even on phone.

(But I’ve not look at storagenode side if this is possible yet).

P/s: type too fast again, maybe providing DNS for storagenode is a superior solution, it will save on memory usage too.

---

<div class="post-metadata">

**Author:** ![Alexey](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/alexey/32/41_2.png) [@Alexey](https://forum.storj.io/u/Alexey)\
**Post date:** [October 2, 2026, 1:31am UTC](https://forum.storj.io/t/database-support-in-the-future/32026/30 "2026-10-02T01:31:31Z")

</div>

> [@kocoten1992](#):
>
> Some strict site will have CSP (content security policy), it only allow js to fetch some specific urls

And what’s a problem if you are the owner of this site? You can apply any rules to it.

---

<div class="post-metadata">

**Author:** ![elek](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/elek/32/9189_2.png) [@elek](https://forum.storj.io/u/elek)\
**Post date:** [October 2, 2026, 8:10pm UTC](https://forum.storj.io/t/database-support-in-the-future/32026/31 "2026-10-02T20:10:21Z")

</div>

> [@kocoten1992](#):
>
> Unrelated, I’m thinking about asking it to support WebRTC on storagenode and a uplink.js on browser side - to bypass gateway entirely, maybe it can get more adoption?

This was considered multiple times. The biggest challenge is that the storagenodes require HTTPS certificate to make this useful.

With the old spiridon satellite I had a PoC to do ACME certificates + dns resolution to the storagenodes. Not impossible, but somewhat tricky (+ fun)

- it’s not really a replacement of a gateway. It’s HTTP protocol support. Not s3.

Would be a good topic to discuss on a SNO Office Hours.

---

<div class="post-metadata">

**Author:** ![kocoten1992](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/kocoten1992/32/7819_2.png) [@kocoten1992](https://forum.storj.io/u/kocoten1992)\
**Post date:** [October 7, 2026, 6:51pm UTC](https://forum.storj.io/t/database-support-in-the-future/32026/32 "2026-10-07T18:51:24Z")

</div>

I’ve been wondering why they don’t publish new version anymore:

> **[CockroachDB Moves to Private Source Code Development](https://www.cockroachlabs.com/blog/source-code-protection/)**
>
> Cockroach Labs explains why future CockroachDB and Pebble source code will be developed privately, while licensing and open source contributions continue.

What would they do if someone train specialized AI to convert binary back to source code? Database as a service?

---

<div class="post-metadata">

**Author:** ![Toyoo](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/toyoo/32/1126_2.png) [@Toyoo](https://forum.storj.io/u/Toyoo)\
**Post date:** [October 7, 2026, 8:30pm UTC](https://forum.storj.io/t/database-support-in-the-future/32026/33 "2026-10-07T20:30:19Z")

</div>

> [@kocoten1992](#):
>
> What would they do if someone train specialized AI to convert binary back to source code?

Lossy, annoying to work with.

Besides, Opus 7 will be able to write an equivalent service from scratch anyway. Opus 8 will do it in a single prompt 🤷

[Previous page](https://forum.storj.io/t/database-support-in-the-future/32026.md?page=1)
