Developer Community

Innovation happens best when everyone has a voice. Instead of relying on a single project manager to funnel feature requests, Cognite Hub solves the bottleneck by enabling all eyes in your organization—or our global community, depending on your preference—to tap in. Whether you are an admin, a developer, or a daily end-user, this is your official space to share frontline insights and directly influence the Cognite Data Fusion product roadmap.Why Submit Your Ideas? Public Ideas: The Product Ideas board is your dedicated space to share requests with the Cognite product team and the community. Submitting publicly allows others to validate, vote on, and build upon your idea! Private Ideas: Submitting privately ensures that feature requests tied to your unique business goals, confidential internal initiatives, or proprietary workflows stay strictly between your organization and Cognite. Track Your Impact: Want a top-level view of your contributions? Upon request, the community team will

 Hi everyone! 👋 Join us tomorrow to see the results of our "Hack for Impact" challenge. We are hosting Tridiagonal.ai (presented by ​@Dinesh Makked ) and SLB (presented by ​@Aditya Kotiyal) to present the winning concepts they developed for "Smart Operations" and "Cognite Vision."This is a fantastic opportunity for the community to: Celebrate the creativity and hard work of your fellow community members. See the specific approach these teams took to build their solutions. Hear the story behind the project directly from the creators. Hope to see you there! 🗓️ Thu, Jan 15 @ 3:00 PM CEST 👉 Register Here

Hi everyone,As we prepare for the General Availability release of Records in CDF on December 2nd, 2025, we're implementing important changes based on learnings from the Private Beta program.Timeline: These changes will be rolled out progressively between today and December 2nd, 2025. We'll update this post as specific changes go live.What's changing:Record-specific containers We are introducing a new type of container dedicated to records, which has higher limits for number of properties, and will allow evolution of the records specific container as more features are made available in records. This container is defined by the usedFor field set to "record". It will be possible to ingest records only into containers with usedFor set to "record" Any records already ingested into non-record containers will remain queryable, but new ingestion attempts to these containers will fail This separation enables better schema management, clearer data organization, and simpler logic for clients q