Localization Speckle

General discussion
1

Hello.
I really like Speckle, I think that such a platform is sorely lacking in my country. But the big problem is that people around me do not know English well and this is off-putting.
I want to get advice on what to do. I made a localized version of Speckle server and connectors, replaced the logo and name in accordance with the license, the domain does not include the speckle name. I want to distribute the localized version in my country. Tell me, should I add a banner with information that Speckle is the main developer, since I only made localization? If so, how to do it? Maybe something else needs to be added, write. I am not a lawyer, but an engineer and a programmer. I will be glad to any additional information

2

Hey there!

Thanks for the kind words. I’m glad you are enjoying Speckle. We are a way off localisation for the time being. Are other AEC platforms you use daily localised to your territory?

We are generally tolerant of the use of the word Speckle in association with the server and connectors technology, so long as it is in the form of knowledge or attribution and not misrepresentation. Everything else is black and white, can or cannot do.

Summary of Your Obligations under Apache 2.0

Requirement Must do?
Include the full Apache 2.0 license text :white_check_mark: Yes
Preserve original copyright headers & NOTICE :white_check_mark: Yes
Strip all Speckle trademarks & branding :white_check_mark: Yes
Publish your own source code :cross_mark: Not obliged
Add a “Powered by Speckle” banner :cross_mark: Not obliged

What You’re Free to Do

  • Fork, modify and rebrand the server and connector code however you like.
  • Translate every string, swap out icons, and add new features or integrations.
  • Distribute binaries or closed-source packages (no obligation to publish your source).
  • Host on your domain, wrap it in your installer or portal, set up custom support, etc.

What You Must Not Do

  • Don’t use any Speckle trademarks or logos.
  • Don’t copy or reuse non-server content (website HTML/CSS, graphics, marketing copy, docs, blog posts, etc.).
  • Don’t imply official endorsement, sponsorship, or affiliation with Speckle, Speckle Systems, or AEC Systems Ltd.
  • Don’t remove or alter the Apache 2.0 license file, original copyright notices, or any required NOTICE statements. Even if you aren’t open-sourcing.

Optional Attribution
You’re under no obligation to surface a “Powered by Speckle” badge—but if you want to be extra friendly, a small footer or About-page note like:

“Built on the Speckle open-source platform (Apache 2.0)”

This is a great way to credit the upstream project and help users discover the original; by implication, they can also find the content we publish in support of the server.

Hope that helps—and happy localising!

2 Likes
3

Thanks for the detailed answer. I want to clarify some details, do I understand correctly that it is necessary to add approximately the following text to each file

/*
* Copyright 2025 AEC Systems Ltd
* Licensed under the Apache License, Version 2.0 (the "License");
*/

or it is enough not to delete the .md and LICENSE files?

4

The terms of the license are that you do not remove any attribution or license information from your code you do not have to add anything