I'm not seeing any built in capabilities or 3rd party applications that provide this capability to Snapcraft directly.
So the typical courses of action for something like this are 1 of the 3 approaches:
- Setup a caching proxy such as Squid or Artifactory and pull your Snappy repositories through one of these. This will create a local cache of the packages as you use them internally.
- Mirror the Snapcraft repositories internally on a system, and pull the artifacts from there instead.
- You may be able to use
parallel to invoke multiple snap commands at the same time to workaround the supposed limitation you're encountering when running one.
Of the 3 options, I typically use 1, and have used 2, for similar situations for other distros packages, not for Snapcraft, but given it's a Canonical product, I don't see why these methods wouldn't work for you as well.
Regarding mirroring
It sounds like mirroring is still something that is being worked on according to this thread - Local mirror for snaps?. But one of the developers mentions that Snapcraft just uses standard HTTP(s) to do the downloading, so any old caching proxy would be able to be used here to keep a local cache of the .snap files.