Esta página se ensambla a partir del portafolio en lugar de estar escrita. Una tecnología solo puede aparecer aquí si uno de los sistemas que describimos realmente la nombra, y cada entrada enlaza a la página sobre ese sistema. Una página de tecnología escrita a mano se convierte en una lista de deseos dentro de un año; esta no puede reclamar algo que no ejecutamos.
No es deliberadamente una lista completa de las cosas con las que estamos dispuestos a trabajar, es la lista de las cosas que operamos nosotros mismos, que es una afirmación mucho más fuerte y mucho más corta.
77 tecnologías, y dónde ejecutamos cada una
- AlertmanagerKnowing something is wrong before a customer tells us
- Android SDKA mobile application, in the stores
- AsteriskOur own telephone network
- cert-managerThe cluster we run our own company on
- Collabora OnlineDocuments, signatures and the paperwork layer
- containerdThe cluster we run our own company on
- Content Security PolicyThis website
- Coqui TTSInference we run ourselves
- coturnOur own video conferencing
- CouchDBOur own telephone network
- DKIMOur own mail servers
- DMARCOur own mail servers
- Docker registryThe cluster we run our own company on
- DovecotOur own mail servers
- FreePBXOur own telephone network
- FreeSWITCHOur own telephone network
- GoOur own telephone network
- GrafanaKnowing something is wrong before a customer tells us
- HibernateA distributed data layer, chosen deliberately
- hreflangTwenty-two languages, done correctly
- ICEOur own video conferencing
- IMAPOur own mail servers
- JavaInference we run ourselvesOur own mail serversDocuments, signatures and the paperwork layerThe attribution pipeline we wrote
- JicofoOur own video conferencing
- Jitsi VideobridgeOur own video conferencing
- KamailioOur own telephone network
- KotlinA mobile application, in the stores
- kube-state-metricsKnowing something is wrong before a customer tells us
- Kubernetes (RKE2)The cluster we run our own company on
- KubeVirtThe cluster we run our own company on
- LibreTranslateInference we run ourselves
- LokiKnowing something is wrong before a customer tells us
- LonghornThe cluster we run our own company on
- MediaMTXOur own video conferencing
- MinIOA distributed data layer, chosen deliberatelyDocuments, signatures and the paperwork layer
- NATS JetStreamThe attribution pipeline we wrote
- next-intlThis websiteTwenty-two languages, done correctly
- Next.jsThis website
- Next.js App RouterTwenty-two languages, done correctly
- Next.js middlewareThe attribution pipeline we wrote
- OllamaInference we run ourselves
- PDFDocuments, signatures and the paperwork layer
- PostfixOur own mail servers
- PostgreSQL wire protocolA distributed data layer, chosen deliberately
- PrometheusKnowing something is wrong before a customer tells us
- ProsodyOur own video conferencing
- push notificationsA mobile application, in the stores
- PythonInference we run ourselvesDocuments, signatures and the paperwork layer
- QdrantA distributed data layer, chosen deliberatelyInference we run ourselves
- RabbitMQOur own telephone network
- ReactThis website
- React NativeA mobile application, in the stores
- RedisA distributed data layer, chosen deliberately
- RspamdOur own mail servers
- RTPOur own telephone network
- ScyllaDBA distributed data layer, chosen deliberately
- self-hosted machine translationTwenty-two languages, done correctly
- SIPOur own telephone network
- SPFOur own mail servers
- Spring BootInference we run ourselvesOur own mail serversDocuments, signatures and the paperwork layerThe attribution pipeline we wrote
- SRTPOur own video conferencing
- Tailwind CSSThis website
- TempoKnowing something is wrong before a customer tells us
- Tesseract-class OCRDocuments, signatures and the paperwork layer
- TraefikThe cluster we run our own company on
- Trusted TypesThis website
- TypeScriptThis websiteA mobile application, in the stores
- UbuntuThe cluster we run our own company on
- UmamiThe attribution pipeline we wrote
- ValkeyA distributed data layer, chosen deliberately
- WebRTCOur own video conferencing
- WebSocketA mobile application, in the stores
- WhisperInference we run ourselves
- WOPIDocuments, signatures and the paperwork layer
- XML sitemapsTwenty-two languages, done correctly
- XMPPOur own video conferencing
- YugabyteDBA distributed data layer, chosen deliberatelyThe attribution pipeline we wrote
Cómo elegimos
La pregunta nunca es cuál es la mejor tecnología, sino cuál de ellas su equipo, o el nuestro, puede seguir operando en tres años cuando algo se rompa en una hora inconveniente. Usaremos algo desconocido cuando el problema lo exija genuinamente, y diremos claramente cuando un proyecto necesite algo fuera de lo que ejecutamos en lugar de aprenderlo a su costa.
Cuéntanos lo que estás tratando de hacer
Una breve conversación suele ser suficiente para saber si somos las personas adecuadas, si no lo somos, lo diremos y le indicaremos un lugar mejor.