
Formed in 2009, the Archive Team (not to be confused with the archive.org Archive-It Team) is a rogue archivist collective dedicated to saving copies of rapidly dying or deleted websites for the sake of history and digital heritage. The group is 100% composed of volunteers and interested parties, and has expanded into a large amount of related projects for saving online and digital history.
History is littered with hundreds of conflicts over the future of a community, group, location or business that were "resolved" when one of the parties stepped ahead and destroyed what was there. With the original point of contention destroyed, the debates would fall to the wayside. Archive Team believes that by duplicated condemned data, the conversation and debate can continue, as well as the richness and insight gained by keeping the materials. Our projects have ranged in size from a single volunteer downloading the data to a small-but-critical site, to over 100 volunteers stepping forward to acquire terabytes of user-created data to save for future generations.
The main site for Archive Team is at archiveteam.org and contains up to the date information on various projects, manifestos, plans and walkthroughs.
This collection contains the output of many Archive Team projects, both ongoing and completed. Thanks to the generous providing of disk space by the Internet Archive, multi-terabyte datasets can be made available, as well as in use by the Wayback Machine, providing a path back to lost websites and work.
Our collection has grown to the point of having sub-collections for the type of data we acquire. If you are seeking to browse the contents of these collections, the Wayback Machine is the best first stop. Otherwise, you are free to dig into the stacks to see what you may find.
The Archive Team Panic Downloads are full pulldowns of currently extant websites, meant to serve as emergency backups for needed sites that are in danger of closing, or which will be missed dearly if suddenly lost due to hard drive crashes or server failures.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Enterprise developers have asked for more flexibility in how they use Copilot. Many teams already work with specific large language model (LLM) providers and maintain custom models tailored to their needs. Copilot has long provided high‑quality GitHub‑hosted models by default, but until now, teams could not connect their own organization’s preferred models directly.
Bring your own key (BYOK) now makes it possible to connect API keys from supported providers including Anthropic, Microsoft Foundry, OpenAI, and xAI to GitHub Copilot. Once connected, all models tied to that key can be used in Copilot Chat on GitHub.com and in supported IDEs. Usage through BYOK is billed directly by your chosen provider and does not count against GitHub Copilot request quotas. This allows teams to take advantage of existing contracts or credits while keeping access managed at the organization or enterprise level.
BYOK_Ent_updated_1080.mp4
Here’s what’s new
Connect your provider’s API key to Copilot
Enterprise admins can add API keys at the enterprise level, and organization admins can add keys at the organization level. Connecting a key lets you choose models from the linked provider for use with GitHub Copilot.
Manage models centrally
Once models are available through a connected key, enterprise admins decide which organizations in the enterprise can use them. Organization admins configure access within their organization.
Both enterprise and organization admins can enable, disable, and configure models from a single settings area. This centralized control ensures consistent setup and allows teams to quickly adapt as needs change.
Use BYOK models in supported IDEs
BYOK is available in Agent, Plan, Ask, and Edit modes in the latest releases of Visual Studio Code, JetBrains IDEs, Eclipse, and Xcode.
Billing handled by your provider
API calls made through BYOK are billed according to your provider’s terms and do not count against GitHub Copilot usage quotas. You can use your existing credits or enterprise agreements with your provider.
Known limitation
BYOK does not support the OpenAI Responses API. Models configured to use a Responses endpoint will not work. BYOK requires the OpenAI Completions API.
Start using BYOK today
BYOK is available now in public preview for GitHub Enterprise and Business customers. Connect your LLM provider’s API key in your enterprise or organization settings and start using your models in Copilot Chat and supported IDEs. Learn more by visiting our documentation.
Help us shape the future
We are just getting started and your feedback will help guide what comes next. Join the discussion below to share feedback and connect with other developers.
Disclaimer: The UI for features in public preview is subject to change.
Beta Was this translation helpful? Give feedback.
All reactions