Request to Add Unkey as a Plugin in Weweb

Ask us anything
1

Hi Weweb Community,

I hope this message finds you all well. I am writing to propose the addition of a new plugin to our Weweb platform: Unkey, an open-source API manager.

As many of you know, managing APIs efficiently and securely is crucial for the success of our projects. Unkey offers a robust solution for this with its comprehensive features, including:

  • API Key Management: Easily create, manage, and revoke API keys.
  • Rate Limiting: Protect your APIs from abuse by setting rate limits.
  • Analytics and Monitoring: Gain insights into API usage and performance.
  • Access Control: Implement fine-grained access control to ensure security.
  • Open-Source Flexibility: Customize and extend Unkey to fit specific needs.

Integrating Unkey as a plugin within Weweb would greatly enhance our ability to manage APIs seamlessly, improving both security and efficiency.

I believe many members of our community would benefit from this addition, and I encourage you to check out Unkey’s features and potential benefits.

Cheers!

2

:white_check_mark: +1

3

it looks like it’s something you should run in your server, not really weweb’s territory :upside_down_face:

1 Like
4

Yeah, it indeed is intended to ron on a backend

2 Likes
5

yes of course, doesn’t mean it has no relevance toward having it in native workflows or else
you can build yours on your backend and connect to the editor like a Stripe plugin for eg
I might miss something here since you seems to be seeing something i don’t :thinking:

6

the library is meant to run on the server where your api runs, for example in a supabase edge function or in you xano endpoint, to implement the features you need. weweb’s plugins that have a server part do a single specifit task and they are completely isolated from your backend.

1 Like
7

Yeah i think that i understood it, i’ve seen it like Stripe that has a Supabase wrapper and integration, but has still an integration in WeWeb

I probably miss few blind spot here, in my initial idea, the integration would have been a simplier to assign an weweb user to a given user unkey (on its own backend) through workflows
same kind of actions where Resend can be used using Supabase function in WeWeb but with proper integrtion it’s was in my mind a way to reduce the complexity and have a “shortcut” action in a weweb workflow

But seem that i misunderstood. the whole picture !
Thanks guys for your insights !

Edit: The initial post yeah is kind of misleading with this message (i use on the first post a quick way to make a text in proper english (the reason you see an readable english :sweat_smile:)i should make a better one even if it change nothing !