Exciting News: Apillon’s Embedded Wallets Are LIVE on Product Hunt
Hey Polkadot enthusiasts!
At Apillon, we’ve been working hard to simplify Web3 adoption for everyone. Our Embedded Wallets SDK is the latest step in this mission, enabling Web2 applications to seamlessly integrate wallet functionality. With this feature, any app can now support Web3 interactions like token transfers, NFT minting, and more—no deep blockchain expertise required.
Why This Matters to Polkadot
Apillon is built with Polkadot’s ecosystem in mind, empowering developers to access its advanced infrastructure with ease. By abstracting the complexities of multi-chain integrations, we’re helping bring the vision of interoperable, user-friendly Web3 solutions to life.
This means:
- Faster Development: Unified APIs for seamless Polkadot parachain integration.
- Broader Adoption: Tools like Embedded Wallets bridge the gap between Web2 and Web3.
- Stronger Ecosystem: Simplifying dApp creation to encourage more projects within Polkadot.
Help Us Spread the Word!
Today we’re showcasing Embedded Wallets on Product Hunt! We’d love for the Polkadot community to show their support by exploring our launch. If you find value in what we’re building, feel free to share your thoughts, feedback, or simply give us an upvote. Every bit of support helps amplify Polkadot’s influence in the Web3 space.
[Link to Product Hunt Launch Page—]
Friendly Reminder:
While Product Hunt celebrates authentic feedback, they discourage any direct solicitation for votes or reviews. So, we kindly ask you to check out the page, engage genuinely, and share what you truly love about the Embedded Wallets feature. Your support means the world to us and helps drive Web3 innovation forward!
Thank you, Polkadot fam! Let’s make waves together.
2 Likes
I was trying to understand the pricing… What is the pricing for, exactly?
Per “developer”/app or for each user?
I assume it’s the former, but then how does it work for community, self-hosted apps? Should each user who self-hosts apply for API key, in that case? That would be fine (like ChatGPT, etc. API keys) - I’m just trying to understand.
Also the storage and wallet count - if every self-hosting user can serve 100 wallets from his setup, that’s easy to understand, but what about “Storage: 3 GB lifetime”? Is that some cloud-hosted encrypted DB as a service, even in Community Edition?
What could a self-hosted (Free) user do once they hit it - wipe the app and start again?
I tried to find out more but clicking on the Community Edition button, but that didn’t seem to work. I assume once that content becomes available, it will be clearer how different tiers work.
My use case is a free, mostly self-hosted Web3 app that doesn’t generate any revenue, so I’m thinking if random, self-hosting users of this app could still it with your Community Edition. And how would that differ from (say) using the same app at a for-profit publicly available Web site with a paid plan/tier.
Community edition is an equivalent of our open source - Apillon is fully open source. I apologise for the community link not working at the moment, we will fix that asap.
Regarding pricing and smaller projects like yours. There is no need to self host since Apillon is offering a generous freemium plan which works across all our services (you will get 1200 credits upon account creation). This amount of credits will allow you to onboard up to 1000 users (depending on which services you predominantly use) or even more.
If you want to use our embedded wallets:
- Create Apillon account
- Create new EW instance
- Follow the docs for SDK and check out the premade code snippets in different Frontend frameworks we have already prepared.
If you run out of credits in the future and you would like to further use Apillon, contact me or any other team members, we will send some credits your way so you can start scaling
here is the link to the embedded wallets docs:
1 Like