Sabitlenmiş Tweet
Documenso
1.7K posts
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
253 Takip Edilen6.3K Takipçiler
Documenso retweetledi
English
Documenso retweetledi
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. 🛠️
English
Documenso retweetledi
🌱⚖️
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
Documenso retweetledi
Done.
How do I get @OpenAI to use @Documenso for document signing now?
Sam Altman@sama
@catalinmpit welcome to the light side!
English
Documenso retweetledi
@catalinmpit @documenso What's the word on part 11 compliance for this?
English
Documenso retweetledi
April 2023: 0 documents signed.
April 2026: 800,000 documents signed.
And we'll reach 1,000,000 very soon.
@documenso's marketing is to ship and let the product do the talking. This is the result.
English
Documenso retweetledi
Always go with @documenso first. 🫡
Michael K. | Automate business & gain time@MichalAiWorld
speedrun how to waste a day: 1. don't read the pricing page 2. implement DocuSeal for a client 3. discover Pro at $20/mo barely adds anything (crazy..) 4. discover SMS verification costs extra -> even self-hosted (!) 5. rewrite everything with Documenso (& sleep well) but hey, at least I know how NOT to do research now 🫠
English
Documenso retweetledi
speedrun how to waste a day:
1. don't read the pricing page
2. implement DocuSeal for a client
3. discover Pro at $20/mo barely adds anything (crazy..)
4. discover SMS verification costs extra -> even self-hosted (!)
5. rewrite everything with Documenso (& sleep well)
but hey, at least I know how NOT to do research now 🫠
English
Documenso retweetledi
i think i messed up
i asked Claude Code to "build a Docusign clone with zero errors"
i guess it took it too literally, and immediately spawned 3 million employee agents who don't do anything
so far all they've done is create a Slack and ask "any update on this?" to each other all day
lesson: startups are hard
English
@rapaccinim @mitgeniusz @levelsio We are a US-based company, but we are citizens of the world 🌎
EU-based customers can claim real sovereignty with our self-hosting plans though: documenso.com/self-hosted
English
English
How is DocuSign worth almost $10 billion but the combined companies of Pieter @levelsio is worth only about $10 million or so?
captain MIT Phd Inventor of Email@mitgeniusz
Docusign is now worth 9.2 billion USD
English
Documenso retweetledi
Friends don't let friends build signing infrastructure
Timur Ercan 🌏@ElTimuro
Too many teams still build signing from scratch. At first, it looks easy. Render a PDF, add a signature field, store the file. Done. And for a while, that works. Until it doesn’t. You start running into edge cases. Multiple signers, ordering, approvals, audit trails, document integrity, storage and versioning. Then identity comes in. Who actually signed this, how do you prove it, what happens if it is challenged. Suddenly you are not building a feature anymore. You are rebuilding infrastructure. This is where most teams hit a wall. You either keep patching your own system or you move to a SaaS tool that does not really fit your product. And now you are working around someone else’s limitations. The problem is not that teams build it. The problem is that signing looks simple on the surface, but has a very deep tail. Signing is not a feature. It is infrastructure. That is how we think about it at Documenso. You should not have to rebuild the hard parts, but you also should not lose control over your workflows. So instead of a closed product, we are building a platform you can embed, extend, and adapt to your own stack. documen.so/platform No need to build signing from scratch. We already did it for you. If you are building product experiences that include signing, we should talk.
English