Documenso

1.7K posts

Documenso banner
Documenso

Documenso

@documenso

The Open Source DocuSign Alternative. https://t.co/fsvxtkU15E https://t.co/pqEsc2PfHT https://t.co/iwhinPSzHv https://t.co/hfwCfzUWPD

Katılım Kasım 2022
260 Takip Edilen6.4K Takipçiler
Documenso retweetledi
Catalin
Catalin@catalinmpit·
Huge milestone: we reached 1,000,000 COMPLETED documents at @documenso.
Catalin tweet media
English
4
4
53
3.7K
Documenso
Documenso@documenso·
Recent abuse incidents made us rethink our email-sending architecture. Before: all emails came from one domain. After: sending is split across domains based on the plan type. This reduces the risk of bad actors hurting email deliverability for everyone. documenso.com/blog/splitting…
Documenso tweet media
English
1
4
17
2.6K
Documenso retweetledi
Catalin
Catalin@catalinmpit·
I realized I don't talk enough about @Documenso... So here’s one of my favorite features: using Documenso without using Documenso. 🫡 With Documenso embedding, you can add document signing to your app without building all the infrastructure yourself. Your users can create and configure documents directly from your product. The recipients can sign there too. They never have to leave your app! The video shows the embedded editor running inside an app. Next, I’ll demo the signing flow too.
English
1
1
16
2.4K
Documenso
Documenso@documenso·
Due to ongoing abuse on the platform, we have temporarily disabled email sending for new free plans. You can still create signing links and share them manually. Existing plans (paid or unpaid) are not affected. We’ll share further updates as the situation evolves.
English
0
0
2
392
Documenso retweetledi
gauravnick
gauravnick@gauravnickk777·
GM EVERYONE ☀️ DSA & OS: LC: 3 questions My first PR was officially merged TY @documenso PROJECTS : Kafka Integration: Successfully linked the Product and Payment services. The product-service now sends messages to the broker, which are received by the payment-service. 🛠️
gauravnick tweet mediagauravnick tweet media
English
2
2
11
576
Documenso retweetledi
commit
commit@commitvc·
OSSCAR Emerging rundown #30 => #26 Continuing the OSSCAR countdown for the emerging category! 🌱 #30 Documenso ships LibPDF, a TypeScript-native PDF library for parsing, modifying, and generating PDFs without the usual API patchwork @documenso
commit tweet media
English
2
1
7
434
Documenso
Documenso@documenso·
🌱⚖️
Timur Ercan 🌏@ElTimuro

We’ve updated our fair use policy to be even clearer. All Documenso plans come with effectively unlimited volume and very open usage policies, especially around signing and API usage. The fair use policy exists to define the intended scope of each plan, so we can allow people to do significantly more without forcing rigid limits, hard caps, or permission-first approvals everywhere. Instead of enforcing strict usage ceilings upfront, we review edge cases when usage clearly outgrows the purpose of a plan. This gives people more freedom to build, experiment, automate, and scale without constantly worrying about hitting arbitrary ceilings. It also lets us be more generous where it makes sense, and charge more where it’s genuinely warranted. Does this occasionally lead to discussions? Yes. Is it worth it? Absolutely. This approach lets us support far more experimentation, growth, and usage within our ecosystem, while still giving us a solid foundation for our commercial offering without turning everything into a permission based process first. This is also an extension of how we think about open source and open companies in general. We’d rather encourage usage, experimentation, and growth wherever it makes sense, then work out sustainable commercial terms collaboratively as value is created. That does not mean unlimited usage without boundaries. It means we prefer cooperative conversations over artificial restrictions and permission first systems. If you have questions about how this applies to your usage, ask us during a sales call. Honestly, in most conversations, the answer is simply: “You’re well within scope. You’re good.” The policy exists mostly so we can support edge cases and extreme scale without punishing everyone else with rigid limits upfront. If you’re building something valuable, we want you to succeed. If we need to talk, we will. If not, keep going. No surprise shutdowns. No forced upgrades. No games. documen.so/fair

ART
0
0
2
1.1K