> ## Documentation Index
> Fetch the complete documentation index at: https://docs.goldsky.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Frequently asked questions

> Collection of frequently (and not-so-frequently) asked questions.

export const CalBooking = ({inline = false}) => {
  useEffect(() => {
    (function (C, A, L) {
      let p = function (a, ar) {
        a.q.push(ar);
      };
      let d = C.document;
      C.Cal = C.Cal || (function () {
        let cal = C.Cal;
        let ar = arguments;
        if (!cal.loaded) {
          cal.ns = {};
          cal.q = cal.q || [];
          d.head.appendChild(d.createElement("script")).src = A;
          cal.loaded = true;
        }
        if (ar[0] === L) {
          const api = function () {
            p(api, arguments);
          };
          const namespace = ar[1];
          api.q = api.q || [];
          if (typeof namespace === "string") {
            cal.ns[namespace] = cal.ns[namespace] || api;
            p(cal.ns[namespace], ar);
            p(cal, ["initNamespace", namespace]);
          } else p(cal, ar);
          return;
        }
        p(cal, ar);
      });
    })(window, "https://app.cal.com/embed/embed.js", "init");
    window.Cal("init", "website-intro", {
      origin: "https://app.cal.com"
    });
    window.Cal.ns["website-intro"]("ui", {
      cssVarsPerTheme: {
        light: {
          "cal-brand": "#FFAD33"
        },
        dark: {
          "cal-brand": "#FFAD33"
        }
      },
      hideEventTypeDetails: false,
      layout: "month_view"
    });
  }, []);
  if (inline) {
    return <div className="my-6">
        <cal-inline cal-namespace="website-intro" cal-link="team/goldsky/website-intro" style={{
      width: '100%',
      height: '600px'
    }} config="{&quot;layout&quot;:&quot;month_view&quot;}" />
      </div>;
  }
  return <button data-cal-namespace="website-intro" data-cal-link="team/goldsky/website-intro" data-cal-config="{&quot;layout&quot;:&quot;month_view&quot;}" className="inline-flex items-center justify-center px-6 py-3 text-base font-medium text-zinc-950 bg-[#FFAD33] rounded-lg hover:bg-[#FFBF60] transition-colors duration-200 cursor-pointer">
      Schedule a call
    </button>;
};

## Subgraphs

<AccordionGroup>
  <Accordion title="Do my subgraph requests need to be authenticated?">
    Endpoints are by default publicly accessible but you can make your endpoints
    private so that it's only accessible by authenticated users, see [private
    endpoints](./subgraphs/graphql-endpoints). Regardless of the access type,
    endpoints are typically rate-limited preventing abuse, and are not publicly
    indexed or searchable. As a best practice, you may want to proxy your
    requests to prevent leaking your endpoint URL from your front-end.
  </Accordion>

  <Accordion title="A subgraph I deployed instantly synced to 100%. Is that an error?">
    No! If Goldsky has already indexed that subgraph (unique subgraphs
    identified by their IPFS hash), it will sync instantly, though you will be
    provided your own endpoint with your own rate limits applied. Query away.
  </Accordion>

  <Accordion title="How many requests can Goldsky handle on a subgraph?">
    By default, the Scale plan is restricted to 50 requests every 10 seconds.
    However, our Enterprise plans scale horizontally and our highest-use
    endpoints are seamlessly handling thousands of requests a second at peak. If
    you need a higher rate limit than what you have enabled on your account,
    please contact us!

    <CalBooking />
  </Accordion>

  <Accordion title="Do Goldsky subgraphs support subscriptions?">
    Not at the moment, though similar functionality for “live queries” can be
    accomplished by polling our querying endpoints. We also do support webhooks,
    which can be similarly useful for certain push-based use cases.
  </Accordion>

  <Accordion title="I keep getting 524 errors with instant subgraphs, what is wrong?">
    Deployments with a lot of metadata can sometimes time out the IPFS server.
    You can try again (right away, and if that isn't working, a bit later) and
    eventually one attempt should work. This is a limitation of the IPFS server,
    but we're exploring options to workaround this. If you continue to face
    issues, contact our support team at
    [support@goldsky.com](mailto:support@goldsky.com) and we'll help manually
    port it over.
  </Accordion>

  <Accordion title="I am getting a 'store error' issue, how do I fix it?">
    You may get `store error: column "x" specified more than once` when using
    Goldsky's [Instant Subgraphs
    functionality](/subgraphs/guides/create-a-low-code-subgraph). Multiple ABIs
    might be causing name conflicts due to conflicting fields or event names in
    the ABI. You can try splitting multiple ABIs into multiple subgraphs. There
    will be a mitigation for this in a future version. If you run into issues
    deploying or with the subgraph separately, contact our support team at
    [support@goldsky.com](mailto:support@goldsky.com).
  </Accordion>
</AccordionGroup>

## Mirror

<AccordionGroup>
  <Accordion title="What region(s) is data sent from?">
    Mirror pipelines write data from `us-west-2` on AWS from a dynamic range of IP addresses. If you need VPC peering / static IPs for your allow list, contact us at [support@goldsky.com](mailto:support@goldsky.com) to discuss your use case.
  </Accordion>

  <Accordion title="Can I set a resource size while creating a pipeline?">
    Yes! Add `--resource size <size>` to your `goldsky pipeline create <name>` command, and the resource size will be set prior to deployment of the pipeline, preventing the need for a pipeline update (which restarts the resource).
  </Accordion>

  <Accordion title="Can a pipeline write to a sink with past data?">
    Yes. The pipeline uses upsert logic (`INSERT ... ON CONFLICT DO UPDATE`), so when a row with the same primary key already exists in the destination, it will be **updated** with the incoming data. This applies to databases that support upserts, such as PostgreSQL, MySQL, and Elasticsearch. For sinks that don't support upserts (e.g., S3), duplicate data will be written.
  </Accordion>

  <Accordion title="How big is each dataset?">
    Your destination sink and indexes kept will vastly influence how much storage you need for your data. We are working on publishing a record count for raw data tables to serve as a starting point for approximation, but in the meantime feel free to contact support for a better estimate for your specific use case!
  </Accordion>
</AccordionGroup>

## Platform

<AccordionGroup>
  <Accordion title="How does Goldsky secure my project API keys?">
    API keys are only kept hashed (meaning after it's displayed for the first
    time, you need to copy and save it locally in order to access it, we won't
    be able to restore it for you!). If your API key is lost, you can reset /
    generate a new one from the settings page in the web app.
  </Accordion>

  <Accordion title="Can I use Goldsky on my custom chain or rollup?">
    Goldsky can support any EVM-compatible chain. If we don't support it in our
    shared indexing infrastructure, contact us to get set up with a dedicated
    indexer. Once set up, we can add new chains to your instance in about an
    hour turnaround time or less.

    <CalBooking />
  </Accordion>

  <Accordion title="Are different versions of the same subgraph charged separately?">
    Yes, every version of a subgraph incurs a separate worker fee and storage
    (in terms of entities) is also counted separately. Be sure to delete old
    versions of a subgraph you no longer need to query to minimize wasteful
    spend.
  </Accordion>
</AccordionGroup>

## Other

<AccordionGroup>
  <Accordion title="How do I pronounce Goldsky?">
    It is pronounced `gold` (like the metal) - `sky` (like the region of the atmosphere we can see). NOT `ski` (like the winter sport).
  </Accordion>

  <Accordion title="Do you have a brand kit?">
    Yes, you can find our brand kit [here](https://goldsky.link/brand-kit). It includes logos, fonts, and other brand assets.
  </Accordion>

  <Accordion title="I have a question not addressed here, can you help?">
    For help with anything else not answered on this documentation page, feel free
    to try the doc-wide search with the top-bar, and if that doesn't help you find
    what you're looking for, don't hesitate to contact our support team at
    [support@goldsky.com](mailto:support@goldsky.com).
  </Accordion>
</AccordionGroup>